Bug 59837

Summary:	Endless loop on processing embedded images that are base64-encoded
Product:	LibreOffice	Reporter:	Marco Fleckinger <marco.fleckinger>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bfo.bugmail, marco.fleckinger
Priority:	medium
Version:	3.5.4 release
Hardware:	x86-64 (AMD64)
OS:	All
See Also:	https://bugs.freedesktop.org/show_bug.cgi?id=52569
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	Document on which this error occured

Description Marco Fleckinger 2013-01-25 08:00:28 UTC

Created attachment 73632 [details]
Document on which this error occured

Expecting endless loop on processing embedded images that are base64-encoded.

Keywords: FILEOPEN, VIEWING, RTL
Program: Writer
Installations:
  OO 3.3, Windows 7 Professional
  LO 3.5.4.2 Build ID: 350m1(Build:2), Debian Wheezey (AMD64), KDE

Originally the problem occured on a Windows machine but I also tried to open the attached file on another machine.

When you try to open the attached document – as any user would do that (:-)) – Writer seems to get into an endless loop while processing the last image.

So I unpacked it, took a look at the content.xml and removed the last picture which was an embedded base64-BLOB, while the prior two were just HTTP-references. After repacking the whole open of the document as expected was possible

I couldn't find a possibility to attach files to a comment of an already existing bug, but I think there may be a conjuction to https://bugs.freedesktop.org/show_bug.cgi?id=52569

Comment 1 bfoman (inactive) 2013-01-25 22:16:21 UTC

(In reply to comment #0)
> I couldn't find a possibility to attach files to a comment of an already
> existing bug

To do this please click Add an attachment link in the Attachments table on a bug's page.

Comment 2 Marco Fleckinger 2013-01-26 15:16:29 UTC

Sorry, could also find it after adding sending this. ;-)

Comment 3 Urmas 2013-01-26 15:47:58 UTC

Confirmed with master. Interestingly, the flat ODF file with the image in question is opened fine.

Comment 4 Robert Roth 2013-02-05 08:25:26 UTC


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