Created attachment 83520 [details] Crash report on OSX I have a document that seems normal enough (it does have a couple of simple formula). When I try to export it as a pdf, libreoffice crashes. I've attached both the source document and crash report.
Created attachment 83521 [details] Source file causing crash
I also downloaded the latest nightly (31/7) and it also crashed.
Hi Peter, Thanks for creating a separate bug for this :-). I can confirm a crash using Mac OSX 10.8.4 with LibreOffice 4.1.0.4 and Version: 4.2.0.0.alpha0+ Build ID: 429148c5f10828c50ae41309942f4946b12a7df9 TinderBox: MacOSX-X86_64@43, Branch:master, Time: 2013-08-02_00:51:34 PS: Thanks for testing the latest version of LibreOffice too! Note my way to make clear which version I used (the Build-ID). You can see the build-ID by going to LibreOfficeDev > About LibreOfficeDev. Kind regards, Joren
Thanks for that Joren, my build-ID for the daily version was: Version: 4.1.1.0.0+ Build ID: b3abb55edd5f6c3168882239df2b4b28dc96cfa For the release version it is: Version: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 I'm using Mac OSX 10.8.4
@peter did you experience the same crash on previous 3.6.x or 4.0.x releases?
No - I created this document in 2009 and made a pdf of it then. Recently I opened it, fixed the formulae (something has changed since 2009 and they no longer displayed correctly), saved the document and exported it - then it crashed. I still have a copy of the original file before I edited it - I've uploaded it in case that's useful too.
Created attachment 83555 [details] Original document created in 2009. This document displayed correctly in 2009 and was successfully exported as a pdf. Now exporting it crashes libreoffice.
Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=a321be22907c47e2e378c494f0de9f3f68af5167 fdo#67660: Fix memory mismanagement crash 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.
Argh, the bug I was fixing was bug #67416 , sorry, I put the wrong bug number in the commit message, but let's hope it has the same root cause as this one.
Yep, same crash as bug #67416 , so let's mark this as a duplicate. *** This bug has been marked as a duplicate of bug 67416 ***
Tor Lillqvist committed a patch related to this issue. It has been pushed to "libreoffice-4-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=20b5932eb6f16b3674592977db56a29fb35ef6f7&h=libreoffice-4-1 fdo#67660: Fix memory mismanagement crash It will be available in LibreOffice 4.1.2. 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.
Still reproducible with Version: 4.2.0.0.alpha0+ Build ID: f30cde45db99d5c57e8be6956bbf824ab92328c2 TinderBox: MacOSX-X86_64@43, Branch:master, Time: 2013-08-09_00:35:4
Emir: I could not reproduce using exactly that daily build. How exactly did you do the PDF export? I just selected File>Export as PDF... from the menu, let all default settings be, clicked the Export button, clicked the Save button, clicked the Replace button when it asked if I wanted to replace an existing w2k_l1_overheads.pdf file. Worked fine. Are you sure you ran the right LibreOfficeDev.app, the one from the daily build in question?
@Tor, Tried once more after deleting the user profile using the same steps, worked fine. Closing as RESOLVED FIXED.
*** Bug 68449 has been marked as a duplicate of this bug. ***
*** Bug 69523 has been marked as a duplicate of this bug. ***
*** Bug 69793 has been marked as a duplicate of this bug. ***
*** Bug 69574 has been marked as a duplicate of this bug. ***