Bug 37470 - [Qt] Image Decoding Test on huge html page - loads forever
Summary: [Qt] Image Decoding Test on huge html page - loads forever
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P2 Critical
Assignee: Viatcheslav Ostapenko
Keywords: Performance, Qt
Depends on:
Blocks: 35784
  Show dependency treegraph
Reported: 2010-04-12 15:27 PDT by rajesh
Modified: 2010-09-22 13:44 PDT (History)
7 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description rajesh 2010-04-12 15:27:37 PDT
Steps to reproduce:
1. Start the Qt Anomaly browser; load the index page 

2. Start the MemLogger, give the name to the log.
3. Return to the Qt Anomaly browser.
4. Select the link “Image Decoding Test” on the index page -> The page
starts loading.
5. Actual results: The page seems to be completely loaded, with all the text
and all the images displayed, however the loading continues forever with the
loading indicator displayed and running. It blocks the our test.

Expected result: The page should stopped loading after the loading is completed
and the loading indicator should disappear.
Comment 1 Simon Hausmann 2010-06-16 23:21:05 PDT
Is this really a release blocking issue? It's neither a crash nor out of memory AFAICS.
Comment 2 Viatcheslav Ostapenko 2010-06-17 09:27:01 PDT
(In reply to comment #1)
> Is this really a release blocking issue? It's neither a crash nor out of memory AFAICS.

As it is described here it doesn't sound critical.
The problem, that it is the same issue we have with loading (cycler, layout) benchmarks. Webkit just cannot load pages reliably on Symbian phone (but works fine on emulator). It looks like one of QNetworkResponses doesn't fire finished event (but content looks loaded).
To reproduce the bug you have to reload page several times and one of loads never finishes (but content looks loaded). That's what loading becnhmark does.
Comment 3 Simon Hausmann 2010-07-02 00:55:50 PDT
Works for me with qtwebkit-2.0 and qt 4.7 on an N8.

I suspect that this may have been a problem in the networking stack not reporting EOF or not delivering all data.
Comment 4 Alexandra Santos 2010-09-01 07:10:26 PDT
This issue is still reproducible with 2.1, for more detail please refer to: https://bsetpl02.americas.nokia.com/browse/QT-3155
Comment 5 Suresh Voruganti 2010-09-01 07:25:04 PDT
As this issue is reproducible with QtWebkit 2.1, re opening the issue
Comment 6 Suresh Voruganti 2010-09-22 13:36:10 PDT
Slava, if this issue is not reproducible, can you pls resolve the error?
Comment 7 Viatcheslav Ostapenko 2010-09-22 13:44:40 PDT
Resolved by platform fixes.