Bug 54760 – [Qt] Simple QML WebView app with Flickable crashes on SegFault in Nokia N8 with Qt 4.7.1 from Qt SDK techpreview

• Component: WebKit Qt
• Status: RESOLVED WORKSFORME

[Aleksi Uotila]

Created attachment 82988 [details]
Sources for the app project, pre-compiled SIS file with Forum Nokia remote compiler

My simple QML test application with WebView causes SegFault when panning the page on N8 PR1.0 with Qt 4.7.1 SIS files from Qt SDK 1.1 tech preview. I also installed Qt 4.7.2 in those this app simply crashes on startup.

The SegFault note is given when launched app via USB debugging in Qt Creator. If ran just without debugging app simply exits.

Steps to reproduce:
(0. Install Qt binaries from Qt SDK 1.1 tech preview)
1. Install the attached SIS file
2. Run the app
3. App should show a list of news feed headers
4. Tap on one of the list items (note: there's no feedback on taps on the list, nor any progress notification when the page starts to load)
5. Wait the page to load
6. You should see checkerboard pattern ones the page is load (this is showed automatically by WebView item) - for some reason the page is presented only once user has panned once the checkerboard. Don't know if this is my apps issue or something too in WebView.
7. When you see the web page pan that page quickly downward - often the app crashes immediately but sometimes one has to pan around quickly.

[Ademar Reis]

Did anybody test this with a recent devel build of QtWebKit? (2.1 branch)

BTW, please follow the Qt template when reporting Qt bugs: http://webkit.org/new-qtwebkit-bug (details on the wiki: http://trac.webkit.org/wiki/QtWebKitBugs)

[Aleksi Uotila]

I made a simple app to check the qt versions I have installed in the device I was experiencing the issue (i.e. crashing):
- Qt version 4.7.2
- OS version 5.2
- Firmware 011.012
- Mobility 1.1.1
- WebKit 534.3

I don't know how to check the WebKit version you mean (2.X...).

[Suresh Voruganti]

Browser team has tested the issue on Qtwebkit 2.1.x and issue is not reproducible.

[Henry Haverinen]

Suresh, we're using 2.1.0 in Qt SDK 1.1 so we should consider that release as well

[Henry Haverinen]

The issue could be related to not setting the EPOCHEAPSIZE to maximum, which  is automatically set in new projects only as of Qt 4.7.2 (see http://bugreports.qt.nokia.com/browse/QTBUG-14472)

[Suresh Voruganti]

Adding Joel

Joel, can you pls look into the issue?

[Aleksi Uotila]

I'm looking into this. I noticed with help from Henry Haverinen that the EPOCHEAPSIZE tag is missing from .pro file as I was using techpreview of Qt SDK. Later SDKs should do this automatically for a developer but still here it's manual.

I'll retest the case tomorrow with increased heap size and report.

[Joel Parks]

 
> I'll retest the case tomorrow with increased heap size and report.

Any update?  Do we re-open this bug?

[Aleksi Uotila]

(In reply to comment #8)
> > I'll retest the case tomorrow with increased heap size and report.
> 
> Any update?  Do we re-open this bug?

Sorry for delay I tested it today. No need to re-open, the issue has been resolved now. However I don't really know what has resolved it. Either it's the symbian:TARGET.EPOCHEAPSIZE = 0x20000 0x8000000 addition to the pro file. Although I'm not 100% sure as I also upgraded more later Qt from Qt SDK 1.1 beta to the device too.

If it was due EPOCHEAPSIZE that is also now resolved in Qt SDK side: Earlier Qt SDK didn't add it automatically but now latest Qt SDK is doing it for new projects and it is even doing it for old projects opened in new Qt Creator if user choses on a dialog prompt to replace the boilerplate files on project open.