Steps how to reproduce [Reproducible] with "LibreOffice 3.6.6.2 rc " German UI/ German Locale [Build-ID: f969faf] {pull date 2013-04-03} on German WIN7 Home Premium (64bit): 1. In WIN Files Explorer go to <C:\Users\user\AppData\Roaming\LibreOffice\3\user> (or similar on your PC) 2. 'Rightclick folder extensions -> Properties - Check "Write Protected"' <ok> 3. In appearing message select 'Apply here, for subfolders and all files' <ok> > Chenages will be applied 4. Launch LibO 5. From Start Center open new empty Writer Document 6. Menu 'Tools -> Options -> Extension Manager' Bug: Runtime Error (for soffice.bin) files with contents will crash after a while without any action, may be even an empty one. Of course these test conditions are quite a stretch, But there might be more sophisticated and hidden situations causing crashes like in "Bug 63240 - CRASH in Tools->Extension manager->Check for updates'. LibO should not crash, but contribute a useful error message.
Created attachment 79324 [details] Bug 63288 - WinDbg session with FAILED_SOURCE_CODE Confirmed with: LO 4.0.2.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Attached full WinDbg session with FAILED_SOURCE_CODE.
NEW as bug confirmed and bt attached.
caolanm->sberg: I got no crash with 4.2 onwards on linux if i chmod -R -w my user dir. Worth a look-see under windows ?
I guess I cannot properly reproduce ths setup from comment 0, as when I go to the Properties of C:\Users\sbergman\AppData\Roaming\LibreOffice\4\user\extensions of a fresh LO master installation on Win 7, "Attributes: Read-only (Only applies to files in folder)" is already checked (as it is for the user directory and all its other sub-dirs, too).
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
Like comment 3, on Linux I got no crash but I can't see any installed extension anymore.
On Win7, I got the same as Stephan's comment (comment 4). May we close this one?
Then lets close as WORKSFORME. (And one isn't supposed to mess with LO's internal file storage, as done in comment 0, in the first place.)