Bug 72362

Summary: [Qt4] tst_QDeclarativeWebView assert
Product: WebKit Reporter: Ádám Kallai <kadam>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Critical CC: allan.jensen, hausmann, jturcotte, michael.bruning, ossy
Priority: P1    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 38654, 79668, 88186    
Attachments:
Description Flags
gdb backtrace for tst_QDeclarativeWebView none

Ádám Kallai
Reported 2011-11-15 00:57:38 PST
Created attachment 115117 [details] gdb backtrace for tst_QDeclarativeWebView gdb backtrace attached
Attachments
gdb backtrace for tst_QDeclarativeWebView (6.05 KB, text/plain)
2011-11-15 00:57 PST, Ádám Kallai
no flags
Michael Brüning
Comment 1 2012-05-16 07:33:40 PDT
Looks as if this is caused by setting the offline web app cache path both in initTestCase and in some test cases themselves... Will have a look.
Michael Brüning
Comment 2 2012-05-16 08:07:07 PDT
Okay, this can only be tested with Qt 4.8 and a WebKit version that builds with it. I don't have a build env for that ready, but my assumption is that the calls to QWebSettings::enablePersistentStorage(tmpDir()); should be removed from the test cases as they will trigger the assert that caused the crash.
Csaba Osztrogonác
Comment 3 2012-11-14 04:46:55 PST
Are we still interested in fixing Qt 4.8 related bugs in WebKit trunk for QtWebKit 2.3 branch?
Allan Sandfeld Jensen
Comment 4 2012-11-14 06:48:33 PST
I think that test has been removed in trunk, and is only present in qtwebkit2.3?
Csaba Osztrogonác
Comment 5 2012-11-14 06:50:31 PST
Good point ... the question is now if we wan't to track a QtWebKit 2.3 only failure here or not?
Allan Sandfeld Jensen
Comment 6 2012-11-14 07:44:28 PST
We have a tracker bug for that
Allan Sandfeld Jensen
Comment 7 2012-11-26 12:18:49 PST
The issue was fixed two weeks ago in 15f943b89cba18a9a758bac32137d5255a9973d3 The problem was that QDeclarativeWebView was not build at all due to a mistake in the qmake file.
Note You need to log in before you can comment on or make changes to this bug.