asked 2015-03-28 09:51:58 +0300
Hi sailors, It seems the native gallery is crashing if one tries to open a very large picture. I've tried to open a externally created jpeg of 9600x6144 pixels, a compilation of smaller pictures merged to a single one.
Did anyone else tried something similar?
M
answered 2015-03-28 10:30:01 +0300
Pics opened should fit into RAM so that they can be handled. In your example, the full resolution takes 121 screens, why the need to watch that on the phone?
Pics opened should fit into RAM so that they can be handled.
They don't. There are number of possible approaches to view huge images, the simplest one for JPEG is to downscale them on decoding. This approach does not impose extra burden on CPU but instead reduces required calculations to get decoded bitmap in memory.
But even assuming dumb approach to just decode image fully: 9600*6144*3(24 bits colour?)/1024/1024=168.75 MiB. Jolla have much more RAM than 169 MiB, why it should not be able to display such image?
answered 2016-03-17 19:11:09 +0300
After all the problem was in the jpeg encoding. The gallery seems to have had a problem with progressive encoding.
Asked: 2015-03-28 09:51:58 +0300
Seen: 353 times
Last updated: Mar 17 '16
Just tested 18000x18000px image of Orion Nebula on my device. It is handled nice and seems to be downscaled on decoding (jolla-gallery uses a bit more 100 MiB to show this image and details are blurred on zooming in).
Can you provide an example image to reproduce crash? It might be unrelated to image size.
Self-Perfection ( 2015-03-29 23:16:36 +0300 )editHi, (is there a way to upload pictures here?)
To reproduce this:
I can open the Orion btw., so you might be right and this is not a memory problem. So whats wrong with the Gimp pictures? And why does it kill ALL other Aps?
Any hints to trace this down?
M
derHorst ( 2015-03-30 08:57:45 +0300 )edit@derHorst
There is, but upload button is available only in question or answer dialog. But you can use uploaded images in comment field as well
Posting here several megabytes image does not look like good idea, however. Please, do find a way to link example image. Your way reproduce involves too many variables and steps. For instance, your default jpeg saving options might be saved options from previous jpg exports and not Gimp defaults.
As for tracking the issue,check logs (
Self-Perfection ( 2015-03-31 13:55:11 +0300 )editdevel-su journalctl -af) while dealing with your image. Also make sure that image is not saved with progressive option, as progressive jpg require much more resources for decoding.Hi,
Have fun with the picture...
And thank you for the hint! Btw. the browser is able to show it.
M
derHorst ( 2015-03-31 21:41:04 +0300 )editYour picture is displayed perfectly well on my device.
Self-Perfection ( 2015-03-31 22:27:19 +0300 )edit