Issue 55158 - One char change takes several seconds when "Record" enabled
Summary: One char change takes several seconds when "Record" enabled
Status: CLOSED DUPLICATE of issue 35762
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOO 2.0 Beta2
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: crash, needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2005-09-28 00:59 UTC by njglin
Modified: 2006-01-11 07:35 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description njglin 2005-09-28 00:59:48 UTC 
Document converted from MSWord 5.3MB in  in size
to about 780KB in odt format.  Full of tables (test steps).
When Edit->Changes->Record is on, changing one character takes several seconds
and CPU usage gets to 50% (it is 2 processor machine).
As soon as Record is checked off, the pace of change is good.
The Record feature is not usable, at least for this document.
Comment 1 flibby05 2005-09-28 08:37:53 UTC 
njglin, thanks for reporting this!
please attach a sample document.
thanks, max, ooo volunteer
Comment 2 flibby05 2005-09-28 18:10:00 UTC 
confirm with m129 pavel janik build on SuSE 9.3
Comment 3 flibby05 2005-09-28 18:11:07 UTC 
bugdoc was sent confidentially,
searching for issues possibly meeting actual scenario
Comment 4 flibby05 2005-09-28 18:20:19 UTC 
hello njglin,
issue 35762 seems to generally match your issue.
you could now
- vote for 35762 for a quicker fix
- cc yourself in 35... and later crosscheck with your own bugdoc
- produce a sample test bugdoc for public upload

again, thanks for supporting us!

Max
Comment 5 flibby05 2005-09-28 18:22:59 UTC 
njglin,
i keep this issue in unconfirmed state,
if you can submit an public bugdoc i will set to NEW,
in case issue 35762 gets fixed and your is solved, too, i will close as double.

oooqa, please keep issue open for now,

thanks,
max
Comment 6 atdsm 2005-12-06 19:11:48 UTC 
-> njglin

Do you still have the issue with OOo 2.0 (Release version) or with 2.0.1RC2
(Development snapshot)? We're in the process of cleaning up old issues and we
need to know whether we can close this issue or not. Your input would be
appreciated, especially a sample file if you are still having the issue with the
2.0 release version.

Thanks,

Steve
Comment 7 michael.ruess 2006-01-11 07:34:13 UTC 
Same problem as issue 35762.

*** This issue has been marked as a duplicate of 35762 ***
Comment 8 michael.ruess 2006-01-11 07:35:42 UTC 
Closing dulicate.