Apache OpenOffice (AOO) Bugzilla – Issue 15021
extreme sloth when resuming work on a file
Last modified: 2004-03-22 09:35:17 UTC
I have found in 1.1 beta 2 that the whole app goes into a kind of paroxysm after I have typed five or six characters into a reopened file. The CPU usage shoots up to nearly 100%, the screen goes dead, and everything stays like that for up to 15 seconds before the CPU usage slides back to normal, and there is a sudden rush of characters onto the screen. This does happen occasionally when working on long files anyway, but there is a reliable way to repeat it: Open a long-ish file (3,000 words or so). this now happens quite fast, or father than it used to. Then start to type something towards the top of the file. Within 20 characters/keystrokes, if not quicker, everythign will stop, as described. Then, just as suddenly, OOo will stop doing whatever it was doing, and return to normal behaviour. This is with windows 2000, SP3, masses of memory and hard disk space, but a fairly slow 400mhz k6-2 processor. Still, there is nothing in this which should make it hard to type.
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 .
.