Bug 247311 - Konqueror with kwebkitpart (and Rekonq) crash when running futuremark peacekeeper benchmark [WebCore::QNetworkReplyHandler::forwardData, ..., KDEPrivate::AccessManagerReply::qt_metacall, KIO::TransferJob::data]
Summary: Konqueror with kwebkitpart (and Rekonq) crash when running futuremark peaceke...
Status: RESOLVED DUPLICATE of bug 253340
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdewebkit (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: webkit-devel
URL:
Keywords:
: 252042 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-11 01:21 UTC by Stanislav Ionascu
Modified: 2010-12-18 19:17 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
New crash information added by DrKonqi (7.03 KB, text/plain)
2010-09-14 16:24 UTC, fsanchez 		Details
New crash information added by DrKonqi (12.20 KB, text/plain)
2010-09-23 22:43 UTC, Sven Assmann 		Details
New crash information added by DrKonqi (10.58 KB, text/plain)
2010-12-16 23:48 UTC, mossad 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Ionascu 2010-08-11 01:21:12 UTC 
Application: konqueror (4.5.00 (KDE 4.5.0))
KDE Platform Version: 4.5.00 (KDE 4.5.0)
Qt Version: 4.7.0
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Went to futuremark peacekeeper  to check the performance of the kwebkitpart

- Custom settings of the application:
Set the kwebkitpart for the *html pages.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ff89055d760 (LWP 23691))]

Thread 4 (Thread 0x7ff87517a710 (LWP 23743)):
#0  0x00007ff88fde4f83 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ff887fd84a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007ff887fd88fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007ff88d8f9bd6 in QEventDispatcherGlib::processEvents (this=0x14705c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007ff88d8cc7b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007ff88d8ccb9c in QEventLoop::exec (this=0x7ff875179db0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007ff88d7d823d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007ff88d8ac6d8 in QInotifyFileSystemWatcherEngine::run (this=0xeacdf0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007ff88d7db1be in QThreadPrivate::start (arg=0xeacdf0) at thread/qthread_unix.cpp:266
#9  0x00007ff88b2fa9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007ff88fdf16fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7ff86ef46710 (LWP 23773)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007ff870494bbe in WTF::TCMalloc_PageHeap::scavengerThread (this=<value optimized out>) at wtf/FastMalloc.cpp:2378
#2  0x00007ff870494cd9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7ff870c4af14) at wtf/FastMalloc.cpp:1497
#3  0x00007ff88b2fa9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#4  0x00007ff88fdf16fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7ff8650a8710 (LWP 23796)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:211
#1  0x00007ff874733081 in ?? () from /usr/lib/libxine.so.1
#2  0x00007ff88b2fa9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#3  0x00007ff88fdf16fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff89055d760 (LWP 23691)):
[KCrash Handler]
#6  0x00007ff8701e2619 in WebCore::QNetworkReplyHandler::forwardData (this=0x104c8f0) at platform/network/qt/QNetworkReplyHandler.cpp:399
#7  0x00007ff8701e3e54 in WebCore::QNetworkReplyHandler::qt_metacall (this=0x104c8f0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5d4515a0)
    at ./moc_QNetworkReplyHandler.cpp:86
#8  0x00007ff88d8e57a7 in QMetaObject::activate (sender=0x1dacbc0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x90) at kernel/qobject.cpp:3280
#9  0x00007ff88ea23a97 in KDEPrivate::AccessManagerReply::qt_metacall (this=0x1dacbc0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5d451710) at ./accessmanagerreply_p.moc:81
#10 0x00007ff88d8e57a7 in QMetaObject::activate (sender=0x1884250, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x90) at kernel/qobject.cpp:3280
#11 0x00007ff88ea58514 in KIO::TransferJob::data (this=0x67006e0069006e00, _t1=0x1884250, _t2=<value optimized out>) at ./jobclasses.moc:388
#12 0x00007ff88ea5acc0 in KIO::TransferJob::slotData (this=0x1884250, _data=...) at ../../kio/kio/job.cpp:1003
#13 0x00007ff88ea5ea46 in KIO::TransferJob::qt_metacall (this=0x1884250, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5d4518f0) at ./jobclasses.moc:368
#14 0x00007ff88d8e57a7 in QMetaObject::activate (sender=0x186ae10, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x90) at kernel/qobject.cpp:3280
#15 0x00007ff88eb0c942 in KIO::SlaveInterface::data (this=0x67006e0069006e00, _t1=<value optimized out>) at ./slaveinterface.moc:146
#16 0x00007ff88eb0fc55 in KIO::SlaveInterface::dispatch (this=0x186ae10, _cmd=100, rawdata=...) at ../../kio/kio/slaveinterface.cpp:163
#17 0x00007ff88eb0cbf3 in KIO::SlaveInterface::dispatch (this=0x186ae10) at ../../kio/kio/slaveinterface.cpp:91
#18 0x00007ff88eb007a6 in KIO::Slave::gotInput (this=0x186ae10) at ../../kio/kio/slave.cpp:344
#19 0x00007ff88eb0098c in KIO::Slave::qt_metacall (this=0x186ae10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5d451d00) at ./slave.moc:82
#20 0x00007ff88d8e57a7 in QMetaObject::activate (sender=0x156d3d0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x90) at kernel/qobject.cpp:3280
#21 0x00007ff88ea2cdf7 in KIO::ConnectionPrivate::dequeue (this=0x156d4a0) at ../../kio/kio/connection.cpp:82
#22 0x00007ff88ea2cf1d in KIO::Connection::qt_metacall (this=0x156d3d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x1917e20) at ./connection.moc:79
#23 0x00007ff88d8df87e in QObject::event (this=0x156d3d0, e=0x67006e0069006e00) at kernel/qobject.cpp:1219
#24 0x00007ff88c9c2cdc in QApplicationPrivate::notify_helper (this=0xc58410, receiver=0x156d3d0, e=0x15a7110) at kernel/qapplication.cpp:4389
#25 0x00007ff88c9c87cd in QApplication::notify (this=0x7fff5d452980, receiver=0x156d3d0, e=0x15a7110) at kernel/qapplication.cpp:4270
#26 0x00007ff88e307eb6 in KApplication::notify (this=0x7fff5d452980, receiver=0x156d3d0, event=0x15a7110) at ../../kdeui/kernel/kapplication.cpp:310
#27 0x00007ff88d8cda8c in QCoreApplication::notifyInternal (this=0x7fff5d452980, receiver=0x156d3d0, event=0x15a7110) at kernel/qcoreapplication.cpp:732
#28 0x00007ff88d8d09b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xc3aa60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xc3aa60) at kernel/qcoreapplication.cpp:1373
#30 0x00007ff88d8fa043 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#31 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#32 0x00007ff887fd48c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x00007ff887fd8748 in ?? () from /lib/libglib-2.0.so.0
#34 0x00007ff887fd88fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x00007ff88d8f9b83 in QEventDispatcherGlib::processEvents (this=0xc3a560, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#36 0x00007ff88ca747ee in QGuiEventDispatcherGlib::processEvents (this=0x67006e0069006e00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007ff88d8cc7b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#38 0x00007ff88d8ccb9c in QEventLoop::exec (this=0x7fff5d452750, flags=) at kernel/qeventloop.cpp:201
#39 0x00007ff88d8d0c4b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#40 0x00007ff89015507e in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../../apps/konqueror/src/konqmain.cpp:234
#41 0x00007ff88fd29c4d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fff5d453288) at libc-start.c:226
#42 0x00000000004006b9 in _start ()

Possible duplicates by query: bug 245945.

Reported using DrKonqi
Comment 1 fsanchez 2010-09-14 16:24:21 UTC 
Created attachment 51641 [details]
New crash information added by DrKonqi

konqueror (4.5.1 (KDE 4.5.1)) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:
I was surfering some pages (bancofrances.com.ar & movistar.com.ar/online) and suddenly, Konqueror + Webkit crashed

-- Backtrace (Reduced):
#9  0x00007f3bbd62baa7 in KDEPrivate::AccessManagerReply::qt_metacall (this=0xf65a00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb7115450) at ./accessmanagerreply_p.moc:81
[...]
#11 0x00007f3bbd660524 in KIO::TransferJob::data (this=0xe93720, _t1=0xe887a0, _t2=<value optimized out>) at ./jobclasses.moc:388
#12 0x00007f3bbd662cd0 in KIO::TransferJob::slotData (this=0xe887a0, _data=...) at ../../kio/kio/job.cpp:1003
#13 0x00007f3bbd666a56 in KIO::TransferJob::qt_metacall (this=0xe887a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb7115630) at ./jobclasses.moc:368
[...]
#15 0x00007f3bbd714982 in KIO::SlaveInterface::data (this=0xe93720, _t1=<value optimized out>) at ./slaveinterface.moc:146
Comment 2 Sven Assmann 2010-09-23 22:43:35 UTC 
Created attachment 51926 [details]
New crash information added by DrKonqi

rekonq (0.4.0) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

open the URL: http://service.futuremark.com/peacekeeper/run.action

-- Backtrace (Reduced):
#6  0x00007f1a76b58619 in WebCore::QNetworkReplyHandler::forwardData (this=0x20ce6a0) at platform/network/qt/QNetworkReplyHandler.cpp:399
#7  0x00007f1a76b59e54 in WebCore::QNetworkReplyHandler::qt_metacall (this=0x20ce6a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff70ddfcd0)
    at ./moc_QNetworkReplyHandler.cpp:86
[...]
#9  0x00007f1a79470aa7 in KDEPrivate::AccessManagerReply::qt_metacall (this=0x265fcf0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff70ddfe40) at ./accessmanagerreply_p.moc:81
[...]
#11 0x00007f1a794a5524 in KIO::TransferJob::data (this=0x0, _t1=0x26392b0, _t2=<value optimized out>) at ./jobclasses.moc:388
#12 0x00007f1a794a7cd0 in KIO::TransferJob::slotData (this=0x26392b0, _data=...) at ../../kio/kio/job.cpp:1003
Comment 3 Dario Andres 2010-11-18 17:02:21 UTC 
*** Bug 252042 has been marked as a duplicate of this bug. ***
Comment 4 Dawit Alemayehu 2010-11-19 00:06:32 UTC 
Believe it or not, this is both an upstream and downstream issue at the same time! Why may all ask ? Well it is because the only I was able to duplicate this bug is when I compile QtWebKit in debug mode and then split the debug symbols from the generated library into a separate debug library using objcopy and striped out the debugging symbols from the original library. 

As such I can only assume that the distro(s) in question here follow the same method outlined above to create their qtwebkit packages. If that is the case, then that is where the problem needs to be addressed. I was originally unable to reproduce this issue originally because my QtWebkit was compiled in release mode...
Comment 5 Andrea Diamantini 2010-11-19 01:14:07 UTC 
(In reply to comment #4)
> Believe it or not, this is both an upstream and downstream issue at the same
> time! Why may all ask ? Well it is because the only I was able to duplicate
> this bug is when I compile QtWebKit in debug mode and then split the debug
> symbols from the generated library into a separate debug library using objcopy
> and striped out the debugging symbols from the original library. 
> 
> As such I can only assume that the distro(s) in question here follow the same
> method outlined above to create their qtwebkit packages. If that is the case,
> then that is where the problem needs to be addressed. I was originally unable
> to reproduce this issue originally because my QtWebkit was compiled in release
> mode...

Uhm... let me say that I ever compiled QtWebKit in debug mode, striping out the symbols.
I ever could reproduce the issue with rekonq or konqueror, but never with arora.
Comment 6 Dawit Alemayehu 2010-11-19 02:36:30 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > Believe it or not, this is both an upstream and downstream issue at the same
> > time! Why may all ask ? Well it is because the only I was able to duplicate
> > this bug is when I compile QtWebKit in debug mode and then split the debug
> > symbols from the generated library into a separate debug library using objcopy
> > and striped out the debugging symbols from the original library. 
> > 
> > As such I can only assume that the distro(s) in question here follow the same
> > method outlined above to create their qtwebkit packages. If that is the case,
> > then that is where the problem needs to be addressed. I was originally unable
> > to reproduce this issue originally because my QtWebkit was compiled in release
> > mode...
> 
> 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.

For me, I cannot reproduce this issue with konqueror + kwebkitpart if I compile qtwebkit in release mode...
Comment 7 Dawit Alemayehu 2010-11-19 07:49:58 UTC 
BTW, do any of you get a warning dialog about the script running for a long time and whether or not you want to stop it ?
Comment 8 Andrea Diamantini 2010-11-20 19:03:11 UTC 
(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. BTW, I'll try compiling QtWebKit in release mode and test it with the 3 browsers.
Comment 9 Andrea Diamantini 2010-11-20 19:04:43 UTC 
PS: Can I reduce the title length to "Konqueror with kwebkitpart (and Rekonq) crash when running futuremark peacekeeper benchmark" ?
:D
Comment 10 Dario Andres 2010-11-20 19:08:56 UTC 
@Andrea: You can reduce the lenght of the title but consider that bug triagers use the backtrace functions in the title to identify the master crash report when handling duplicates. Leaving the first function only may still work.
Regards
Comment 11 Andrea Diamantini 2010-11-20 19:25:23 UTC 
On Saturday 20 November 2010 19:08:56 Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=247311
> 
> 
> 
> 
> 
> --- Comment #10 from Dario Andres <andresbajotierra gmail com>  2010-11-20
> 19:08:56 --- @Andrea: You can reduce the lenght of the title but consider
> that bug triagers use the backtrace functions in the title to identify the
> master crash report when handling duplicates. Leaving the first function
> only may still work. Regards

Ah, ok. Dario, thanks for clarification. You switched on a light in my bugzilla 
knowledge :)
Comment 12 Dario Andres 2010-11-24 21:43:43 UTC 
[Comment from a bug triager]
Note: bug 253340 is now grouping crashes with a similar/the same backtrace but under different situations (no related to this benchmarking site). The root cause may still be the same.
Regards
Comment 13 Dawit Alemayehu 2010-11-27 22:17:59 UTC 
On Sat, Nov 20, 2010 at 1:03 PM, Andrea Diamantini <adjam7@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 ?
Comment 14 Laurent Bonnaud 2010-12-13 14:59:25 UTC 
I see the same crash in Ubuntu maverick with the following package versions:

Package: konqueror
Version: 4:4.5.4-0ubuntu1~maverick1~ppa1

Package: rekonq
Version: 0.6.1-0ubuntu1

Package: libkdewebkit5
Version: 4:4.5.4-0ubuntu1~maverick1~ppa2

Package: libqtwebkit4
Version: 2.0.0-0ubuntu1
Comment 15 markuss 2010-12-13 16:28:08 UTC 
Just scrored 2152 points with rekonq (which was identified as Konqueror) and Qt 4.7.1.
I think whatever caused the crash has been fixed in Qt 4.7.1
Comment 16 mossad 2010-12-16 23:48:18 UTC 
Created attachment 54839 [details]
New crash information added by DrKonqi

rekonq (0.6.1) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:
Peacekeeper's rendering test phase cused crash

-- Backtrace (Reduced):
#11 0x03dd0ec7 in QIODevice::readyRead (this=0xa49f260) at .moc/release-shared/moc_qiodevice.cpp:91
#12 0x0223e896 in KDEPrivate::AccessManagerReply::appendData (this=0xa49f260, kioJob=0x8fed590, data=...) at ../../kio/kio/accessmanagerreply_p.cpp:168
#13 0x0223e9be in KDEPrivate::AccessManagerReply::qt_metacall (this=0xa49f260, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbfcf9b54) at ./accessmanagerreply_p.moc:81
[...]
[...]
#16 0x022774c9 in KIO::TransferJob::data (this=0x8fed590, _t1=0x8fed590, _t2=...) at ./jobclasses.moc:388
#17 0x0227a312 in KIO::TransferJob::slotData (this=0x8fed590, _data=...) at ../../kio/kio/job.cpp:1003
Comment 17 Dawit Alemayehu 2010-12-18 19:17:12 UTC 
For those using a self compiled QtWebKit from git, the crash you get, if any, at this benchmark site is a separate issue unless you are using KDE older than version 4.5.4. Otherwise, the source of this crash has already been addressed. See comment #13 in bug# 253340 for further details.

*** This bug has been marked as a duplicate of bug 253340 ***