[WebKit-devel] [Bug 247311] Konqueror with kwebkitpart (and Rekonq) crash when running futuremark peacekeeper benchmark [WebCore::QNetworkReplyHandler::forwardData, ..., KDEPrivate::AccessManagerReply::qt_metacall, KIO::TransferJob::data]

Dawit Alemayehu adawit at kde.org
Sat Nov 27 22:18:03 CET 2010


https://bugs.kde.org/show_bug.cgi?id=247311





--- Comment #13 from Dawit Alemayehu <adawit kde org>  2010-11-27 22:17:59 ---
On Sat, Nov 20, 2010 at 1:03 PM, Andrea Diamantini <adjam7 at gmail.com> wrote:
> https://bugs.kde.org/show_bug.cgi?id=247311
>
>
>
>
>
> --- Comment #8 from Andrea Diamantini <adjam7 gmail com>  2010-11-20 19:03:11 ---
> (In reply to comment #6)
>> (In reply to comment #5)
>> >
>> > Uhm... let me say that I ever compiled QtWebKit in debug mode, striping out the
>> > symbols.
>>
>> Did you mean to say that "I have never compiled" ? But have you compiled it in
>> debug without doing the rest ? IOW, I was able to duplicate this crash when I
>> did what I stated above. Otherwise, I cannot reproduce the result.
>>
>> > I ever could reproduce the issue with rekonq or konqueror, but never with
>> > arora.
>
> No, I'm saying I always compile QtWebKit in debug mode striping out debug
> symbols. I'm used to with every software I compile from myself.
> I ever... always could reproduce the issue with rekonq and with konqueror +
> kwebkit, but NEVER with Arora.
>
> So, I'm suggesting the issue comes from kio integration.

Well I have never ever been able to reproduce this bug with konqueror
+ kwebkitpart until I compiled QtWebKit in debug mode and stripped out
the debugging symbols into own separate library. I doubt the issue is
in KIO integration especially since we no longer return a NULL where a
QNetworkReply was expected.

Right now there is only one known and outstanding issue with the KIO
integration and that is its inability to properly handle KIO's slave
pause and resume functionality on unknown/unsupported mime-types.

> BTW, I'll try compiling QtWebKit in release mode and test it with the 3 browsers.

Please let me know how that goes. I too have tried this benchmark with
QtTestBrowser, Arora, Konqueror + kwebkitpart and to date I have yet
to see a single crash when QtWebKit is compiled in release mode. Hmm,
can you also try the debug mode version without stripping out any of
the debugging symbols into a separate library ?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the WebKit-devel mailing list