Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | extreme sloth when resuming work on a file | ||||||
---|---|---|---|---|---|---|---|
Product: | General | Reporter: | ingenstans | ||||
Component: | code | Assignee: | thorsten.martens | ||||
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P2 | CC: | issues | ||||
Version: | OOo 1.1 Beta2 | ||||||
Target Milestone: | OOo 2.0 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
ingenstans
2003-05-28 14:46:00 UTC
The same thing hapens without typing. If I have had an OOo window open inthe background for any considerable time, and tnen return to it, clicking the minimise button in the window has the same effect: massive CPU activity for fifteen or twenty seconds, while the computer is completely unresponsive to any kind of input, followed by a sidden return to normal. It's _not_ accompanied by disk trhashing, and happens even with plenty of memory reported free. Andrew, thanks for your responce but it would be helpful, when you could give a step by step description with an available bugdoc. May you have a URL where I can get such doc. Created attachment 6591 [details]
large, but unremarkable doc showing sluggishness on resuming
Damn. The attachment lost my description. Here we go again. 1) Open the enclosed doc (or any other moderately large file) in Windows. I have autosave set to go every five minutes without confirmaiton, but I don't think that's relevant. 2) Leaving the document open in the background, do somethig else for fifteen minutes. I was googling, I think; but anythign not involving OOo should work. Even leaving the computer alone for lunch smight do the trick 3 A) switch back to the document and start typing high up in it or 3 B) press the minimise button in the window. Either way, I get (reliably and repeatedly) a big spike of CPU activity (not disk thrashing) showing up on the task monitor, and everything on the computer goes unrsponsive for ten or twenty seconds. If I am typing through this period, nothing appears on the screen, and then there is a sudden gout, as if it had all been poured out of a buffer. If, instead, I try to minimise the screen, nothin ghappens at all. HI->TM: Can't reproduce, please take over. I don't know what the difference can be, because I'm getting this every time I resume work on a document now, whether they're short or long, or wherever I start typing in them. I can type about four characters and then (minimised) task manager zooms up to 100% and stays there while nothing appears onthe screen, however much I keep typing. After about 15-20 seconds, the task manager clears, and all the letters I have typed pour into the text. CPU 1.7GHz RAM 256MB PC doesn't freeze, but CPU usage spikes all the way to 100% Seems to be fixed in 1.1 rc1, so I will mark this closed worksforme . . |