This bug report pertains to LibreOffice Writer Version: 6.4.0.0.alpha0+ Build ID: 096b91ee15e2686d4eb7118fdb9688ba9dbc44b2 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-09-14_17:42:26 Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded Today I downloaded this version and it happened several times that it froze. When I looked at the task manager, I saw no or almost no CPU load from LibreOffice Writer. I have no idea what triggers the freezing, but it happened several times and I saw no specific pattern regarding what I did last. After ending LO Writer despite it was not responding, of course all my edits were lost. At least the document could be recovered to the state when I started with it. Please give ans demand what I shall look for on the next occasion of such a freeze.
Adalbert, does it happen with different documents or only with one documents or with similar documents (for example large documents or complex table structure or many comments, ...). If this is the case, please attach such a document if possible. => NEEDINFO
I have the impression it happened with larger documents, at least much more often. It just happened again with a 243 pages document, a logbook which accumulated in many sessions. But it also happened in editing smaller files. I'll try to construct one by putting together parts from publicly available sources.
[Automated Action] NeedInfo-To-Unconfirmed
I have tried to build such an example from non copyrighted sources. However they did not show the freezing deficiency. Since a two weeks newer development version is available, I'll quit searching for a publishable example of file now. Unfortunately I don't see a status to assign for this thread now. The status selection of this forum is limited to NEW/UNCONFIRMED/ASSIGNED/NEEDINFO/REOPENED/RESOLVED/DUPLICATE. Today I'll download the more recent development version of 2009-09-28 and forget about the bug in 2009-09-14.
Adalbert, you can't confirm your own bugs => Status back to UNCONFIRMED
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Xisco, I have first moved the directory ~/.config/libreoffice/4/user to some other place. Then I started the newer version of LibreOfficeDev, which I had just installed in the safe mode. Then I did some editing in the safe mode with one of the files with which I encountered freezes. I did not encounter a freeze or a crash during this half of an hour editing time. I could not confirm the bug in safe mode. Then I cloesd LibreOfficeDev again and restored the user directory with the profile. When I restarted LibreOffice, I continued working on the file which I tried before and luckily I did not encounter any crash. When I restored the profile directory user, I saw an adjacent directory ~/.config/libreoffice/4/crash, which contained some dump files. However, none of them was from the time when I reported this bug. Is the generation of crash dumps in this place disabled for development versions?
(In reply to Adalbert Hanßen from comment #7) > I could not confirm the bug in safe mode. > > Then I cloesd LibreOfficeDev again and restored the user directory with the > profile. When I restarted LibreOffice, I continued working on the file which > I tried before and luckily I did not encounter any crash. Adalbert, so we can close this bug report (You can reopen it, if freezing will appear again)?
(In reply to Dieter Praas from comment #9) > (In reply to Adalbert Hanßen from comment #7) > > I could not confirm the bug in safe mode. > > > > Then I cloesd LibreOfficeDev again and restored the user directory with the > > profile. When I restarted LibreOffice, I continued working on the file which > > I tried before and luckily I did not encounter any crash. > > Adalbert, so we can close this bug report (You can reopen it, if freezing > will appear again)? Closing