| Summary: | [Qt4] tst_QDeclarativeWebView assert | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Ádám Kallai <kadam> | ||||
| Component: | Tools / Tests | Assignee: | 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: |
|
||||||
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. 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. Are we still interested in fixing Qt 4.8 related bugs in WebKit trunk for QtWebKit 2.3 branch? I think that test has been removed in trunk, and is only present in qtwebkit2.3? Good point ... the question is now if we wan't to track a QtWebKit 2.3 only failure here or not? We have a tracker bug for that 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. |
Created attachment 115117 [details] gdb backtrace for tst_QDeclarativeWebView gdb backtrace attached