Problem description: When leaving LO Writer idle for a while and I then try to re-focus to one of its Windows, it becomes unresponsive, continously using about 40% of my CPU time. I then have to end the process via the task manager and restart the program. Steps to reproduce: Not sure. The freezing happens apparently random, about once a day. The bug only started appearing since I upgraded to 4.0.2.2. I don't have any complex documents opened when this happen. Operating System: Windows 7 Version: 4.0.2.2 release Last worked in: 4.0.1.2 release
Does it occur even with just having a blank document open? How many documents do I need open to verify it? How long do I have to leave it idle (10 minutes, 10 hours?) Marking as NEEDINFO - we need as much info as possible to reproduce the problem. When you say only appeared when you upgraded to 4.0.2.2 release, what did you upgrade from? Lastly, have you tried a fresh profile? https://wiki.documentfoundation.org/UserProfile Please provide as much detail as you can as this is a nasty one if it can be confirmed then mark the bug as UNCONFIRMED. Thanks!
(In reply to comment #1) > Does it occur even with just having a blank document open? How many > documents do I need open to verify it? How long do I have to leave it idle > (10 minutes, 10 hours?) It has happened with anything from one to maybe 5 documents open. Usually they include .doc files. Idle time is probably a minimum of 2 hours, often much longer (1-2 days), though. Sometimes the computer goes into standby during that period, sometimes not. > When you say only appeared when you upgraded to 4.0.2.2 release, what did > you upgrade from? Upgrade was from 4.0.1.2 > Lastly, have you tried a fresh profile? > https://wiki.documentfoundation.org/UserProfile I have a large number of customizations, auto-complete dictionaries etc. and need Writer for productive use daily. So this is a bit tricky. Maybe I can try the fresh profile on the weekend. > Please provide as much detail as you can as this is a nasty one if it can be > confirmed then mark the bug as UNCONFIRMED. Thanks! Please let me know if I can provide any other info. Thanks!
My suggestion is just to backup your profile and test a fresh profile, then as soon as you confirm that the problem still exists, delete the fresh profile, and bring your backup back ~ of course be VERY CAREFUL to backup as you said you have a lot of customization. The fact that you have so much customization makes the chance that it's a profile issue slightly higher - especially if you have a lot of extensions installed.
kliems: in addition to what Joel said, you should also give a try to 4.0.3. I don't pretend your problem will be solved for sure but perhaps it may help.
Small update: I've been working on an .odt document for the past two days and did not have any .doc files open. And didn't have any crashes. Since the time between crashes is somewhat unpredictable, I'm not sure if there is a causal link, but I'll test further. @Julien: Yes, will update today.
I've updated to the latest version (4.0.3.3) today and the problem persists. I now suspect it has something to do with the type of documents open. So far I have not had a crash when I had only .odt documents open. Once I also had a .doc open the problem re-appeared. I'll try again tomorrow with a clean user profile.
Installed a new user profile last weekend and have not had the described kind of crash since then. I guess this bug can be closed.
kliems: thank you for your feedback. If you still have the old LO profile, could you zip it and attach it by using this link (https://bugs.freedesktop.org/attachment.cgi?bugid=64561&action=enter)?
Created attachment 79615 [details] Backup of user profile, as requested.
Just some thinkings: - I saw you used Java 1.7 but do you use Java 64 or 32 bits? - I noticed you had Zotero, do you reproduce the problem if you disable it? - registrymodifications.xcu (the main file in LO directory profile) is quite customized, you may to delete only this one? Of course, you must first copy your old backup profile and use it as current one. Of course, you can also put it as RESOLVED/WFM since it may be quite difficult to pinpoint the problem on the profile.
Well, from my perspective it's resolved. Should the issue re-appear when I install some add-on or similar I suppose I can re-open it.