Created attachment 134716 [details] Activity Monitor showing LibreOffice and Google Chrome during high CPU usage When using Writer and Safari (or Google Chrome) on a thesaurus page (thesaurus.com, Merriam Webster, Free Dictionary) for several hours or more, CPU usage goes way up until Writer hangs (e.g. slow keyboard response or page redraw, dropdown menus don't display, Save stalls in the middle of the process, etc.). Usually Safari Web Content becomes unresponsive at the same time. Finder may also become unresponsive. The same behavior occurs with Chrome. If the thesaurus page is running video ads, CPU usage drops the moment the thesaurus page is closed. But CPU usage also goes way up on Free Dictionary with only one static ad. Going back and forth from editing in Writer to finding words on the browser page over time appears to cause Writer to hang. This problem exists for NeoOffice as well.
@Allegra : 1) without step-by-step reproducible instructions, this will likely never be confirmed - unconfirmed bugs remain that way until after a certain time of inactivity, they get marked resolved invalid (it still takes nearly a year for that to happen). 2) It appears hard to correlate a problem with LibreOffice with what might be memory management problems in either Safari and/or Google Chrome - certainly Google Chrome is known to be a memory hog in and of itself. What is meant by that is that other than you noticing an increase in system resources when all of these programs are running together, we need some more tangible evidence of cause/effect. 3) For example, does the problem occur in Writer when only Writer is running in the GUI - if so, under which particular circumstances does that occur (e.g. spellchecking, document containing active links to internet resources, etc )? That would point to memory leakage directly in the LibreOffice application. 4) There are already known reported bugs where all session resources gradually get consumed when running LibreOffice - perhaps what you describe is just another instance of such behaviour. If you can provide us with a reproducible test scenario, then I can attempt to reproduce the behaviour and hopefully confirm the bug. Setting to NEEDINFO Please set back to UNCONFIRMED once you have provided the requested information, and a sample document where this behaviour is displayed (unless it happens with any simple/empty Writer document).
At this point we believe Writer may be a contributing factor to high CPU usage, but not the cause of it. In any case, it's impossible to identify a specific set of actions in Writer that lead to the problem (other than type, cut, and paste for 4-5 hours at a time). Or, as you say, this could be another example of session resources being consumed. Since submitting this bug, we've had indications that malware on the router might be involved, and since we made the router more secure, we haven't seen any sustained high CPU usage to cause LibreOffice to hang. Feel free to mark this RESOLVED if appropriate.