Bug 65594

Summary: EDITING: Crash when trying to remove a named bitmap
Product: LibreOffice Reporter: dany franck <dany.franck>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dtardon, michael.stahl
Priority: medium Keywords: regression
Version: 4.0.4.1 rc   
Hardware: Other   
OS: Windows (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: Error messages and delphi code
The used model with the bitmap
Attachment contains a macro reproducing the problem
Contains a macro (supprimerimage) producing the crash

Description dany franck 2013-06-10 06:41:41 UTC
Created attachment 80598 [details]
Error messages and delphi code

Problem description:

A delphi programm pilots LO via DCOM. It opens a model with text and three bitmaps. It happens that one of the bitmaps had to be removed in the document. In this version, LO crashes on the command page.remove(object) (also in 4.1b1). 
The delphi code and then messages are reproduced inthe first attachment. The model is the second attachment.
All works fine in previous versions.

              
Operating System: Windows 7
Version: 4.0.4.1 rc
Last worked in: 4.0.3.3 release
Comment 1 dany franck 2013-06-10 06:44:30 UTC
Created attachment 80601 [details]
The used model with the bitmap
Comment 2 dany franck 2013-06-17 07:21:37 UTC
Created attachment 80933 [details]
Attachment contains a macro reproducing the problem

The supposed bug was detected with a program under DCOM. The crash can be reproduced with a macro.
The document contains the macro SupprimerImage. The crash happens on maPage.remove(monImage)
Comment 3 dany franck 2013-06-18 05:53:13 UTC
Created attachment 80982 [details]
Contains a macro (supprimerimage) producing the crash

The macro caused the same crash as the Dcom program. The crash happens on the removal of one of the bitmaps.
Comment 4 Michael Stahl (allotropia) 2013-06-20 21:28:11 UTC
fixed in LO 4.0.5.1 by commit 7096efde95732b613dfa76df61a343b96ec6f979

... so this problem did not just affect ReportBuilder but ordinary Writer documents too...

*** This bug has been marked as a duplicate of bug 64279 ***