Bug 57387

Summary:	Problems working with large pictures
Product:	LibreOffice	Reporter:	J. Zeller <zeller>
Component:	LibreOffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	jorendc, lucasbetschart
Priority:	medium
Version:	3.6.3.2 release
Hardware:	Other
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description J. Zeller 2012-11-22 00:16:24 UTC

Importing large pictures (e.g. jpg, 10000x7000) in writer or draw does not work. Sometimes the Error "No GraficFilter" appears, sometimes "no vaild format" or sometimes the picture is just black (depends on size and how imported).
Downscaling the picture (in an other programm) to e.g. 50% works fine.

In 3.4 this problem does not! occur. I can import exactly the same file without problems. Files safed with 3.4 can be loaded in 3.6, but the picture is not shown.

Comment 1 Lucas Betschart 2012-12-16 18:47:00 UTC

Confirmed with Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)

I have used this picture (Size: 14.8 MB, jpg, Earth at nigth):
http://naturalearth.springercarto.com/ne3_data/16200/textures/5_night_16k.jpg

Error Message: "Graphics filter not found"  (BTW: This text is not translated. I'm using the German version).

Occurs in Writer and Draw.

Importing a 9.7 MB JPG-picture works.

Comment 2 Jorendc 2012-12-28 09:29:16 UTC

Thanks for reporting.

I can confirm this behavior.

When I add several big pictures to Calc, after some images I only can insert 'Black images' (insert -> picture -> from file...). The other images in the document aren't affected.

All the images I used in the spreadsheet are scaled down (I did so (on purpose) not a bug or something). Maybe this bug can lead to a new future: reduce image resolution/size when scale down image. Otherwise this option can interfere with 'Original Size' button. If the image resolution is scaled down, this button ('original size') would be useless when we would like to go back to a big image with the best resolution.

Comment 3 J. Zeller 2013-08-24 09:41:01 UTC

Bug is solved in Version 4.0.3. Can be closed, thanks.