This bug was filed from the crash reporting server and is br-8962ed3b-a646-401b-b68f-b983d1ede6c5. ========================================= I had been editing an old .doc file, mostly clearing direct formatting, and then decided to Reload the document, at which time LO crashed.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Created attachment 143079 [details] Anonymized version of file that crashed This is anonymized version of the file that I was editing when the crash occurred. I had done some editing (mostly removing highlighting, I think, either by setting No Fill or by clearing direct formatting) when I did a Reload and LO crashed.
The crash signature is the same as in bug 115065, so it seems related to table manipulation. However, I can reproduce the crash... @Robert, have you been able to reproduce it again ?
I made one unsuccessful attempt to reproduce the crash, making some changes similar to the ones I made before (but not as many) and then reloading. There are no tables in the document. Xisco Faulí, are you saying that you can or cannot reproduce the crash?
(In reply to robert.funnell from comment #4) > I made one unsuccessful attempt to reproduce the crash, making some changes > similar to the ones I made before (but not as many) and then reloading. > > There are no tables in the document. Yep, I noticed it after opening the document :D > > Xisco Faulí, are you saying that you can or cannot reproduce the crash? No, I can't reproduce it
Not reproduced on Windows or Linux, 6.0 or master. Did some editing before reloading.
No repro with Version: 6.2.0.0.alpha0+ Build ID: 84ccbb5123fe976a105e97390141ed209c8b9bcc CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: x11; Version: 6.2.0.0.alpha0+ (x64) Build ID: 2c85607101e2e04e870e3b87362f39f9a9148e6c CPU threads: 1; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-16_00:12:37
Hi Robert, have you been able to reproduce the crash again? If not, I'd suggest to close this issue.
No, I haven't been able to reproduce it. Maybe the bug should be left open so somebody sometime might consider adding more error checking to the code where it crashed?
(In reply to robert.funnell from comment #9) > No, I haven't been able to reproduce it. > Maybe the bug should be left open so somebody sometime might consider adding > more error checking to the code where it crashed? We can always reopen it if needed. Setting to RESOLVED INSUFFICIENTDATA