Created attachment 113002 [details] Writer will crash when closed while endless loop macro running Writer will chrash when closed while a macro is still running. Attached is a document which demonstrates it by starten an endless loop macro. This behavior was not like this in LibreOffice 3.5
On pc Debian x86-64 with LO Debian package 4.3.3, I could reproduce this. However, I don't reproduce this with: - master sources (future 4.5.0) updated today. - 4.4 sources updated 2 days ago - 4.3 sources updated some days ago. Could you give a try to last stable LO version (4.3.5)?
I verified LibreOffice 4.3.5 on Debian 7.8 , it also chashes the document. To be presice I used Version: 4.3.5.2 Build-ID: 3a87456aaa6a95c63eea1c1b3201acedf0751bd5 I also found a workaround! If I start the macro, then (instead of closing the application window) just close the document by clicking the x olmost in the upper right of the window and after that close the application window by clicking the x in the upper right - than the document is not chrashed after a restart of writer.
Sorry, I just found out, my workaround does not work in all cases. It just works, if I give the application a little time, between closing the document and closing the application. If I am very fast, close the document and in the same second also close the application window, the macro seems to be still running and therfore still chrashes the document.
Well, how come nothing happens? The needed info is given tree days ago: LibreOffice still crashes! I expect either more qustions or a status change. By the way, OpenOffice crashes even harder...
Thank you for your feedback. For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and give it a new try? Put it at NEW meanwhile since I reproduced it too.
OK, so what I did and found out: I renamed ~/.config/libreoffice to ~/.config/libreofficeXXX I started libreoffice 4.3.5.2 Writer installed without languagepack I recognized the File/Recent Documents list was not empty, but reset to an old one, so I figured: "It still gets some defaults from somewhere" I found and renamed ~/.openoffice.org Still the old Recent Documents list, but macrosecurity went up to high I set macrosecutity to medium so I can execute the unsigned macro I opend the attached CrashWriterMacro.odt, answered to enable macros, clickt the CommandButton and closed the application window. I started LibreOffice Writer again, it shows the LibreOffice Document Recovery window with CrashWriterMacro.odt in the list with status not recovered yet
** 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.5 or 5.1.0) 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: 2016-02-21
Created attachment 125590 [details] this moves the crash from the current place to later on Not a particularly useful patch unfortunately. We will still crash later. Basically we have quit during execution of the macro, which is a tricky problem.
https://gerrit.libreoffice.org/#/c/26565/ is a fix which seems to work well for me, detect exit during macro execution, stop all macros, block quit, wait until that macro inner-event-loop finishes, then relaunch quit
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=68cf256f506d4601a2d2cf3ec2d56713afd491e6 Resolves: tdf#88985 block app from exiting during macro execution It will be available in 5.3.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a97e344ba06b92e5f1fc96062a5ad03fb732615e Revert "tdf#88985 block app from exiting during macro execution" It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.