Apache OpenOffice (AOO) Bugzilla – Issue 78063
odt from OO.o 2.1 crashes M213 while reading external OLE object
Last modified: 2013-08-07 14:42:39 UTC
as said in summary writer-file established with O3 2.1 crashed the 680_M213 - recovery restarted - and failed (sorry - file not available - business stuff) Martin
please attach the offending document to this issue, so that we can reproduce and fix the problem here. You can also send the document directly (mru@openoffice.org) for the case it contains confidential data. Feel free to re-open the issue when you've done. Thanks for supporting us!
Cannot reproduce with 680m214 on WinXP. Will later try on Win2000.
If you can't provide us with the document, can you create a crash dump instead? In case you send the crash report to Sun you will get a report id back some time later. By adding this id to this issue you can help us investigating the problem. Without a document to reproduce the problem or a crash report do post mortem debugging we can't do anything about this issue. If you want you can send your document to mru or me by e-mail, confidentiality is guaranteed. If that wasn't possible, perhaps the document still crashes in m213 if you replace confidential parts of it by dummy text in 2.1 so that you can send it to us?
We already recieved the document and we could reproduce the crash on SBA's Win2000 machine. Currently we are waiting for the crash report database to return a stack so that we can see in which area the crash can be located (to cut down the document to the root cause and get the responsible developer).
Confirming issue. SBA, did you already recieve the crash data?
Crash report ID is r8yprc.
MRU->MAV: AMA found out that it crashes due to the OLE object. In the header of the document there is an MS bitmap object which causes the crash. It did not crash in OO 2.2 or 2.2.1 so we have to fix it for 2.3 branch.
MAV->MRU: I can not reproduce the problem in SRC680/m221. Could you please verify this. I took a look to integrated cws's and it looks like there were big changes in writer, that probably have fixed the problem. Actually, usually this stack appears when the writer uses embedded object container from deleted shell, so it is quite possible that it was caused by a problem in writer that was already fixed.
Yes, indeed. This problem has also been solved by the other fixes in the OLE area.
Closed, works weel again in current OO 2.3 build 680m221.