I want to open a file that I created with OO 3.2 and opening the file crashes LibreOffice 3.3 with the following message: Microsoft Visual C++ Runtime Library Runtime Error Program soffice.bin abnormal program termination It also crashes LibreOffice Portable with the same message. Other files are opened fine. Please contact me if you need the file - it is private.
Of course we will need the file to be able to find out what causes the crash.
Is there someone whom I can send it to privately - do not want to see the file here downloadable on the net
@Marc: You can send it to Tor or to me!
Created attachment 43097 [details] Doc with embedded picture
Created attachment 43098 [details] Doc without picture
It looks like LO 3.3 does not like the picture embedded. OO 3.2 and 3.3 have no problem with it.
Please don't send it to me unless I ask for it. And note that I am not promising not to show it to others if you do send it to me.
Created attachment 43100 [details] Picture embedded in doc This picture is embedded in the file. It was created with MindManager Pro 7.2.374
[Reproducible] with "LibreOffice 3.3.0 RC4 - WIN7 Home Premium (64bit) German UI [OOO330m19 (build 6 / tag 3.3.0.4)]". LibO Crashes when I scroll down to see the picture. This one might be related to or DUP of Bug 33785 - Particular WMF causes crash. I will leave a comment there.
Depends on 33785 for now!
Strange. I can work with emf-pictures produced by Stata 11 without any problems in LO 3.3.
Problem is not solved with LO 331 RC1. See attachement. Don't know if 33785 made it into RC1 - release notes do not say so...
Created attachment 43254 [details] Screenshot OO33 vs LO 331 Import of the emf-picture in OO 33 and LO 331 - LO does not crash anymore but the result is not good either
Looks good in RC2
That's good news! Due to <https://bugs.freedesktop.org/page.cgi?id=fields.html#status> we should used FIXED only if a known fix has solved the problem; if the problem only disappeared without known reason, please use WORKSFORME.
*** This bug has been marked as a duplicate of bug 33785 ***