Bug 93843 - once saving and closing an ODT while leaving LibO open the program crashes and automatically goes into recovery mode of the saved files
Summary: once saving and closing an ODT while leaving LibO open the program crashes an...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-01 21:00 UTC by rchammett
Modified: 2016-11-08 13:10 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Error Message after crash (74.90 KB, text/plain)
2015-09-12 09:05 UTC, mgriffin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rchammett 2015-09-01 21:00:12 UTC
LibreOffice v5.0.0.5 has crashed dozens of times since loading. It occurs when exiting the saved file and leaving the LibreOffice program open. The entire program will automatically close and you get a message that it is going through the file recovery process. The recently saved file or multiple files are all recovered without loss.
I have uninstalled and reinstalled the program but the problem persist. I can find no information online concerning how to resolve this problem.
Comment 1 tommy27 2015-09-02 15:42:26 UTC
LibO 5.0.1.2 is out. you should do a complete uninstall and then upgrade and retest.
Comment 2 rchammett 2015-09-02 22:16:28 UTC
I did the uninstall through Windows.  Re-installed LibO 5.0.1.2.  The same
thing happened again.
I saved a new document.  Went up to the small X to close the one file and
leave LibO open.  Program crashed and started up in recovery mode.
Do you have to go through and uninstall any file associated with LibO
before installing v5.0.1.2.
If so, how do you get rid of hidden LibO files?
Comment 3 mgriffin 2015-09-12 09:05:33 UTC
Created attachment 118632 [details]
Error Message after crash
Comment 4 mgriffin 2015-09-12 09:07:31 UTC
The above error was caused by trying to close a file (same effect in writer or calc) using 5.0.1.2 on Mac-OS, it appeared after about a week of normal use, and now the only way to work around the problem was to revert to 4.4.5
Comment 5 Buovjaga 2015-09-18 16:46:40 UTC
How about trying this trick: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile
Comment 6 yxkipsha 2015-11-07 04:22:23 UTC
(In reply to Beluga from comment #5)
> How about trying this trick:
> https://wiki.documentfoundation.org/
> UserProfile#Resolving_corruption_in_the_user_profile

I'd tried and tested. It didn't help. As per my situation, it still happens every time.
Comment 7 Buovjaga 2015-11-07 09:30:42 UTC
(In reply to yxkipsha from comment #6)
> (In reply to Beluga from comment #5)
> > How about trying this trick:
> > https://wiki.documentfoundation.org/
> > UserProfile#Resolving_corruption_in_the_user_profile
> 
> I'd tried and tested. It didn't help. As per my situation, it still happens
> every time.

Well, you are the third person in this report now. I would like to hear from the original reporter and mgriffin.
Comment 8 yxkipsha 2015-11-10 02:29:09 UTC
(In reply to Beluga from comment #7)
> 
> Well, you are the third person in this report now. I would like to hear from
> the original reporter and mgriffin.

Sorry, may I know about how your test result was, as per your suggestion, please?
Comment 9 yxkipsha 2015-11-10 02:30:10 UTC
(In reply to Beluga from comment #7)
> 
> Well, you are the third person in this report now. I would like to hear from
> the original reporter and mgriffin.

Sorry, may I know about how Beluga's test result was, as per your suggestion, please?
Comment 10 rchammett 2015-11-10 03:20:34 UTC
I believe I am the original reporter for this bug.  I have tried all the recommendations I can find.  I have even deleted the newest version of Libre.  Then went through the computer and deleted any prior folders with mention to earlier versions of Libre.  Even went through the registry and deleted anything with the word "Libre" in the line.  Then I downloaded the newest version of Libre 5.0.2.2 and installed to a new folder location.  The crashes of Libre continue, although not as frequent as they were when I first sent in the bug notice.  I have tried to keep note of the occurrences ...ie  whether the crop image tool was used, whether you changed the margins, whether you imported a jpg image, or changed the font type or size.  There seems to be no consistent pattern to the crashes.  I always save the file prior to trying to close the document from either the small X or the program close large X.  It just seems to randomly crash on exit and then automatically comes back up into recovery mode.  Now there have been several occasions when the program says the file/document was unable to be recovered.  Yet it is there and visible where I had saved it prior to closing the document and I can open the file when I want to.  One other thing I have noticed is that periodically in the folder where I save the "odt" files, there will be a file that I saved and then a second file with the same name and just the "#" after the "odt".  I have to delete the "#" before I am able to delete the file.  This does not effect the original file.

After using Open Office and then Libre Office for years this has been the most frustrating situation I have ever had with any program.
Comment 11 Buovjaga 2015-11-10 08:00:21 UTC
(In reply to yxkipsha from comment #9)
> (In reply to Beluga from comment #7)
> > 
> > Well, you are the third person in this report now. I would like to hear from
> > the original reporter and mgriffin.
> 
> Sorry, may I know about how Beluga's test result was, as per your
> suggestion, please?

Well, as "test result", I use LibreOffice for my work every day and I'm not having such random crashes even, if I leave the program open for long periods of tine.
Comment 12 Buovjaga 2015-11-10 08:02:49 UTC
This is quite a tricky issue and one thing that would help bring more information is a backtrace.

Here is the information for Windows:
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

There is a new section on how you can automatically start LibreOffice with the debugger running, so you could more easily catch those crashes, if they don't occur consistently:
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Automation
Comment 13 mgriffin 2015-11-10 15:28:21 UTC
After filing the bug, I reinstalled LibreOffice 4, the problem went away. I worked with 4 until 5.0.2 was released, after which I updated again. Since then the problem has not re-occurred constantly, though it has crashed once or twice on closing documents. I am sorry I cannot provide and more precise information than that.
Comment 14 Buovjaga 2016-03-02 20:40:31 UTC
rchammett: if you test with 5.1.1, do you still get the crashes?
You can try it out by installing with this: https://wiki.documentfoundation.org/SI-GUI

It would also be great to try out the backtracing.
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 15 Xisco Faulí 2016-10-10 11:25:49 UTC Comment hidden (obsolete)
Comment 16 QA Administrators 2016-11-08 13:10:24 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20161108