Description: The attached document was created some time ago. I opened it today, edited it, saved it, and closed it normally. Then then tried to open the document again later, but now whenever I try and open it, Calc crashes out on load with "Bad Allocation". This was originally with 5.0.3.2, but I have now upgraded to 5.2.3.3 and the behaviour is the same. After crashing out, Calc doesn't remove the temporary file (ods#) One thing though - while testing with the new version because it had left the ods# behind, when I tried to re-open it in the old version of LO, I received the "can only open Read Only as file is already open for editing" warning. The file did load successfully like this. But as soon as I deleted the ods# file, it immediately failed to load again as it would try and go into editing mode. Steps to Reproduce: 1. Open the attached document 2. Crash 3. There is no step 3! :-) Actual Results: Crash Expected Results: No Crash Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Created attachment 128581 [details] attached document crashes 100% of the time on load
Unrelated addendum (as I have no idea where to report bugs about the bug tracker) - It asked about the severity as bug-creation time and I set it to "Critical" as that's what it says to do for crashes. However I see that this isn't reflected in the new bug - it's "normal" - if severity is being ignored it probably shouldn't show up at all on the bug-submission page.
Tried loading the document with 5.1.6 and 5.2.3 Linux, no problem.
On pc Debian x86-64 with master sources updated today, I don't reproduce this. For the test, could you apply what is adviced here: https://wiki.documentfoundation.org/QA/FirstSteps ?
No problem. Version: 5.2.3.3 (x64) Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Locale: es-ES (es_ES); Calc: group
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170531
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-20170628