Created attachment 123389 [details] UI screenshot during crash I am a heavy user of Calc. The application crashes very frequently and quite randomly. I could for example copy-paste a value, resize a row, save a document, or perform just about any other typical operation, or do nothing at all and the application will crash. To minimize the impact of the crashes, I set the save AutoRecovery information interval to 1 minute, which I noticed caused even more frequent crashes. I then disabled save AutoRecovery information and the crashes appear to have stopped! It seems to me that the save AutoRecovery contains a bug somewhere that causes the application to crash. Possibly a race condition? I was lucky to take a screenshot (attached) of the interface right at the time of the crash. You will note that the interface has no buttons and UI text at the bottom is distorted. Also note the status bar says "Save Document" with an empty progress bar. The dark spots are my edits to remove private information. This may be related other bugs reporting crashes, but I think I've pinpointed the culprit in this bug report. To reproduce, set save AutoRecovery information to 1 minute interval and begin using the application as a typical user would. In my case I copy-pasted information from a pdf document. After 5-30 minutes it will crash.
Please try resetting the user profile, sometimes solves strange issues. https://wiki.documentfoundation.org/UserProfile Usually it's enough renaming/deleting the file "user/registrymodifications.xcu", it affects all the options in Menu/Tools/Options, and the files "user/basic/dialog.xlc" and "scrip.xlc" are overwritten, additionally custom colors in "user/config/standard.soc" are lost.
Reset the user profile as per recommendation and observed significantly less frequent crashing (about 5-10 times less frequent), but still the application crashes randomly. The fashion in which it crashes is different. I no longer see a distorted GUI, instead the application simply disappears from the screen in an instant. Also, autorecovery information is no longer corrupt and it is possible to restore to the auto saved state. I cannot pin point the issue to help you identify the bug. Any suggestions on what I can do? Is there a debug version I can install that would give more feedback, that I can then convey to you?
What you can try now is disable the option: Menu/Tools/Options/LibreOffice/View - Graphics output - Use OpenGL for ...
Disabled use of OpenGL as per instructions. Still observed a crash in the same fashion as described in my original post (2016-03-07 18:14:34 UTC). Crashes are now infrequent, but not eliminated. I was able to see that it crashed the moment auto save tried to save auto recovery info, and I was not able to recover the information from auto recover. The application was not in use at that time and was idling. I would appreciate further advice to help determine the issue.
If you like you can try to get a backtrace to attach here. https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg Please first try disabling all Graphics output options.
Followed all instructions. Applications crashed about 1 day after being started. The crash was a different than before though, and this time I got an error message first. Unfortunately I did not copy the error message but it said something about threads and the message did not seem to be very user friendly, had text like ::Threads or something along those lines. I've attached the back trace, however it says that symbols are wrong, not sure why, I followed all instructions carefully. Not sure how useful this document will be. Please provide further instructions to help identify the issue.
Created attachment 123542 [details] backtrace
(In reply to sviatoslav from comment #6) > I've attached the back trace, however it says that symbols are wrong, not > sure why, I followed all instructions carefully. Not sure how useful this > document will be. As written in the error message: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. Run '!sym noisy' before .reload to track down problems loading symbols. You can turn it off later with '!sym quiet'.
Ok, I think I have a pretty good backtrace now, see attached. It crashed in the same fashion as originally described in my bug report with the attached UI screenshot.
Created attachment 123606 [details] backtrace
Does it still happen with 5.1.1 btw.?
Using Writer 5.1.1.3 application crashed, but for different reason than the original bug report, therefore we may consider opening a new bug report. At the time of the crash in Writer I clicked on "Format" menu and wanted (and may have) clicked on "Page". Backtrace is attached. Please advise if a separate bug report should be created. Your question regarding the crash happening in version 5.1.1 remains unanswered. I will get back to you after sufficient usage of Calc or a crash.
Created attachment 123844 [details] backtrace Crashed in Writer, not Calc. May need a separate bug report.
please, give an update of the current bug status using latest LibO 5.1.6.2 or 5.2.3.3. thanks.
I have not experienced issues with version 5.2.3.3 or some of the previous versions. Also, the issues stopped without upgrading to a later version, but after an update to windows, which would suggest the bug was somewhere else, other than in LO, possibly in Windows or drivers etc.
Thanks, let's close.