Bug 40637 - [Qt] Large image (jpg) files are not loaded with Qt Anomaly browser.
Summary: [Qt] Large image (jpg) files are not loaded with Qt Anomaly browser.
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Images (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P2 Critical
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2010-06-15 15:01 PDT by Prasad
Modified: 2010-11-05 09:31 PDT (History)
3 users (show)

See Also:


Attachments
HTML file (643 bytes, text/html)
2010-06-15 15:01 PDT, Prasad
no flags Details
Small Image (165kb) (165.57 KB, image/jpeg)
2010-06-15 15:03 PDT, Prasad
no flags Details
Large Image (1.06 MB) (1.07 MB, image/jpeg)
2010-06-15 15:03 PDT, Prasad
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Prasad 2010-06-15 15:01:24 PDT
Created attachment 58825 [details]
HTML file

Large image (jpg) files (Size > 1MB) are not loaded / displayed with Qt Anomaly browser.

Pre-condition:
The Image file should be copied onto the defined location (specified in the HTML file).

Steps to reproduce:
1. Launch the attached html file and the image has to be displayed.

Result: If the image size is greater than 1MB, image is NOT displayed.
        If the Image size is smaller,(lesser than 1MB) the image is displayed properly.
Comment 1 Prasad 2010-06-15 15:03:02 PDT
Created attachment 58826 [details]
Small Image (165kb)
Comment 2 Prasad 2010-06-15 15:03:32 PDT
Created attachment 58827 [details]
Large Image (1.06 MB)
Comment 3 Jukka Jokiniva 2010-06-17 00:10:57 PDT
Sounds like there is not enough applicaion heap to process the image. To be ignored?
Comment 4 Janne Koskinen 2010-08-16 03:47:22 PDT
(In reply to comment #3)
> Sounds like there is not enough applicaion heap to process the image. To be ignored?

4 000px × 2 248px * 32b = ~35MB of raw data to copied least twice in the memory. Yes, this is OOM. Since there is no mention of target device we can only assume limiting factor to be EPOCHEAPSIZE of Anomaly browser.
Comment 5 Janne Koskinen 2010-09-08 06:15:12 PDT
Closed since no further info was provided. Re-open with suggestions what to fix e.g. large images should be scaled down to small-screen/limited memory environment.
Comment 6 Suresh Voruganti 2010-11-05 08:38:13 PDT
Issue is still reproducible. Pls check https://projects.maemo.org/bugzilla/show_bug.cgi?id=183631 for more details.
Comment 7 Janne Koskinen 2010-11-05 09:16:46 PDT
(In reply to comment #6)
> Issue is still reproducible. Pls check https://projects.maemo.org/bugzilla/show_bug.cgi?id=183631 for more details.

Please copy the details over here. Least I cannot access that bugzilla.
If the issue is on Symbian devices why the bug is in maemo.org?
And still as said, it is OOM and we cannot do anything radical about it as is. Image decoding is done in Qt and not in webkit.
Here is one related issue from Qt http://bugreports.qt.nokia.com/browse/QTBUG-14424.

Reporting hardware where the incident is seen is very crucial. When it comes to image RAM usage N8 using VG backend is very different beast than e.g. 5800 Express Music using raster backend.
Comment 8 Suresh Voruganti 2010-11-05 09:31:35 PDT
Dint noticed the OS, As someone commented this bugzilla ID in Maemo bugzilla, i added the comments from that database.

As per your comments, I have moved the Maemo bugzilla error to Qt, so resolving this error as Invalid.