RESOLVED INVALID 107029
[Qt] QtWebKit-based browsers crash with QtWebKit 2.3
https://bugs.webkit.org/show_bug.cgi?id=107029
Summary [Qt] QtWebKit-based browsers crash with QtWebKit 2.3
Filip Brcic
Reported 2013-01-16 10:02:33 PST
Created attachment 183000 [details] Output from the crashing rekonq QtWebKit browsers (tested with rekonq and arora) crash with qtwebkit 2.3git20130115 package for arch linux. The package consists of the latest tarball of the qtwebkit-2.3 branch from gitorious with a single patch that enables settings->acceleratedCompositingEnabled(), taken from the bug https://bugs.webkit.org/show_bug.cgi?id=106892. In attachment I provided backtraces from rekonq (2.0) and arora (0.11.0). They seem to crash because of some fastMalloc call, so this is probably a NULL pointer issue or something in that vicinity. Reverting qtwebkit to qtwebkit 2.2.2 fixes the problem. I am using up-to-date Arch Linux with the following versions of relevant packages: extra/arora 0.11.0-3 community/rekonq 2.0-2 extra/qtwebkit 2.3git20130115-1 extra/qt 4.8.4-1
Attachments
Output from the crashing rekonq (3.37 KB, text/plain)
2013-01-16 10:02 PST, Filip Brcic
no flags
Output from the crashing arora (2.57 KB, text/plain)
2013-01-16 10:03 PST, Filip Brcic
no flags
Filip Brcic
Comment 1 2013-01-16 10:03:11 PST
Created attachment 183001 [details] Output from the crashing arora
Benjamin Poulain
Comment 2 2013-01-17 14:34:23 PST
The crashlog are useless because they are not symbolicated. Can you please attach: -Disassembly at the position of the crash. -Symbolicated crash logs.
Allan Sandfeld Jensen
Comment 3 2013-01-19 13:16:49 PST
The backtraces are not very helpfull, but this bug could be the same as https://bugs.webkit.org/show_bug.cgi?id=104525, in which case it should be solved in the latest version of qtwebkit-2.3
Andrea Scarpino
Comment 4 2013-01-26 07:14:11 PST
On Arch Linux the user who reported this bug solved building qtwebkit with --no-sse2
Allan Sandfeld Jensen
Comment 5 2013-02-05 06:00:54 PST
Thank. I will close the bug assuming it was a problem with wrong instruction set then.
Note You need to log in before you can comment on or make changes to this bug.