Created attachment 124333 [details] Local 1 Saving a Calc sheet after modifying results in freeze / crash. new bug created as not related to 98504. The document is located on a network share, and to eliminate this I created a local disk copy, but got exactly the same error. I thought the issue could be a conflict with the anti virus software attempting to scan the file, so I un-installed the AV, and also got the same result. I can confirm that openGL for rendering is not ticked. It seems to happen most often when you attempt to do something (click in a cell, scroll down the sheet) whilst the save is 'in progress', however as the the reporter stated, sometimes you can leave the machine untouched and it errors on the auto save, therefore not as a direct result of user interruptions. created windows debug info (see attached). I have run a number of times and attached the output. The network 1,2 and Local 4,5 don't give much away. Local 1 doesn't get an error code, but the others are consistent with EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000144
Created attachment 124334 [details] Local 2
Created attachment 124335 [details] Local 3
Created attachment 124336 [details] Local 4
Created attachment 124337 [details] Local 5
Created attachment 124338 [details] Local 6
Created attachment 124339 [details] Network 1
Created attachment 124340 [details] Network 2
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
I have installed 5.2.0.2 and after half an hour of testing I cannot reproduce the crash. I've looked through the release notes and bugs fixes listed against the alpha and beta versions and can't see any one that looks like it directly relates, but it seems to have been resolved.
Thanks for testing! Closing as WORKSFORME — the FIXED status is reserved for issues explicitly closed by a code commit.