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
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.
Is this really a release blocking issue? It's neither a crash nor out of memory AFAICS.
(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.
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.
This issue is still reproducible with 2.1, for more detail please refer to: https://bsetpl02.americas.nokia.com/browse/QT-3155
As this issue is reproducible with QtWebkit 2.1, re opening the issue
Slava, if this issue is not reproducible, can you pls resolve the error?
Resolved by platform fixes.