Created attachment 115195 [details] file created with an older version of LibO Open "libO_bugquitfile.ods", do not change anything and just exit LibO. Then I got this errormessage (2 samples, hex numbers does not stay the same) Error message sample 1: --------------------------- DDE Server Window: soffice.bin - Application Error --------------------------- The instruction at "0x02c5eee5" referenced memory at "0x00000004". The memory could not be "read". Click on OK to terminate the program --------------------------- OK --------------------------- Error message sample 2: --------------------------- DDE Server Window: soffice.bin - Application Error --------------------------- The instruction at "0x7c911669" referenced memory at "0xffffffff". The memory could not be "read". Click on OK to terminate the program --------------------------- OK --------------------------- It seems to me that the error message is more likely to appear when the document was opened by picking it frot the Recent files list. So far I haven't had any loss of data because if changing anytime before quitting LibO, the save file question still appears before the errormessage. Also - I installed this version over version 4.2.5.2. Install steps listed: * Version 4.2.5.2 + aditional offline help file pack installed. * Uninstall help file pack for version 4.2.5.2 * Install LibO version 4.4.2.2 * Install heoffline heilp file pack for version 4.4.2.2 I'm not able to tell if version 4.2.5.2 would have given same error on quit when that file is opened.
Could not reproduce (tried with recently opened, too). You could try getting a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg Win 7 Pro 64-bit, Version: 4.4.3.1 Build ID: b2f347f2ac68821efc00b6f1793cda90af748118 Locale: fi_FI Version: 5.0.0.0.alpha1+ (x64) Build ID: f0edb677f09ad338e22ac3b5d91497b4479e0b3c TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-27_01:54:20 Locale: fi_FI
I can not confirm with LO 4.4.2, win7
Hello, Thank you for submitting the bug. The bug has previously been reported, so this bug will be added as a duplicate of it. You will automatically be CCed to updates made to the other bug. Please specify your OS version, thank you *** This bug has been marked as a duplicate of bug 89696 ***