Bug 15154 – Segmentation fault when running javascript

• Component: WebKit Qt
• Status: RESOLVED FIXED

[Rikardo Tinauer]

I loaded my xhtml file into WebKit (QtLauncher). My xhtml the contains a lot of javascript code and input widgets. The file gets loaded (some errors reported). When I click some input fields and scroll the xhtml up-down a bit it crashes and says segmentation fault.

[Rikardo Tinauer]

Created attachment 16213 [details]
xhtml file containing javascript that crashes WebKit

I suppose javascript in the xhtml file is guilty of crashing WebKit, I have tesed WebKit with variuos sites and html pages with javascripts and I never crshed WebKit since this xhtml file

[Rikardo Tinauer]

I have added attachment that I assume causes the WebKit crash.

[Rikardo Tinauer]

Created attachment 16214 [details]
segmentation fault backtrace

I ran the QtLauncher with my xhtml file and print out backtrace that my xhtml produces

[Rikardo Tinauer]

I forgot to mention that my form sends out AJAX requests, but server was not there when I expirienced a crash, maybe it's relevant information?

[Rikardo Tinauer]

The following crash occured on Linux and Windows

[Rikardo Tinauer]

Bug not closed. Found error.

It is in Troltech's class "QWebNetworkRequestPrivate" in file "WebKit/WebKit/qt/Api/qwebnetworkinterface.cpp".

The error is in line 136 in method "QWebNetworkRequestPrivate::init(...)".
The following code 
"DeprecatedString pd = resourceRequest->httpBody()->flattenToString().deprecatedString();" assumes that server backend always exists or always sends back something. If no server backend "httpBody()" method returns null, I added sanity check for null and code now work perfectly.

I don't know it this bug is to be resolved since I have already reported it to Trolltech. The code is different (I found the same bug in Qt 4.4.0 tp1). They will correct their code and when their code is merged into WebKit the error should disappear.

Rikardo

[Simon Hausmann]

Holger ran into the same crash some time ago. Your fix is identical to what he came up with and correct :). We'll submit it to SVN soon.

[Simon Hausmann]

Fix landed in r29734