Bug 81041 – Crash after several hibernate/resume cycles in WebCore::QNetworkReplyWrapper::resetConnections

• Status: RESOLVED
• Resolution: INVALID
• Component: WebKit Qt

[Raúl]

Hello:

  I'm using Debian sid which currently deploys Qt 4.8.0, QtWebKit 2.2.1, KDE 4.7.4. I use konqueror with webkit kpart as browser. When I have an opened konqueror session for maybe 2 or more hibernate/resume cycles (after been offline) konqueror will crash with the following backtrace:

Thread 1 (Thread 0x7fe90e36a840 (LWP 14276)):
[KCrash Handler]
#6  0x0000003da518c562 in QObject::disconnect (sender=0x2691c60, signal=0x0, receiver=0x24d52c0, method=0x30ad4c9 "receiveMetaData()") at kernel/qobject.cpp:2891
#7  0x0000003d93a921ee in disconnect (member=0x3d94090f0f "1receiveMetaData()", receiver=0x24d52c0, this=<optimized out>) at /usr/include/QtCore/qobject.h:252
#8  WebCore::QNetworkReplyWrapper::resetConnections (this=0x24d52c0) at ../../../Source/WebCore/platform/network/qt/QNetworkReplyHandler.cpp:254
#9  0x0000003d93a9224f in WebCore::QNetworkReplyWrapper::release (this=0x24d52c0) at ../../../Source/WebCore/platform/network/qt/QNetworkReplyHandler.cpp:235
#10 0x0000003d93a923b8 in WebCore::QNetworkReplyHandler::release (this=0x3529e90) at ../../../Source/WebCore/platform/network/qt/QNetworkReplyHandler.cpp:425
#11 0x0000003d93a923fe in WebCore::QNetworkReplyHandler::abort (this=0x3529e90) at ../../../Source/WebCore/platform/network/qt/QNetworkReplyHandler.cpp:413
#12 0x0000003d93a8f509 in WebCore::ResourceHandle::cancel (this=0x7fe8a9fb3be8) at ../../../Source/WebCore/platform/network/qt/ResourceHandleQt.cpp:107
#13 0x0000003d93883d3c in (anonymous namespace)::PingLoader::~PingLoader (this=0x7fe8a9baa910, __in_chrg=<optimized out>) at ../../../Source/WebCore/loader/PingLoader.cpp:130
#14 0x0000003d93883de9 in (anonymous namespace)::PingLoader::~PingLoader (this=0x7fe8a9baa910, __in_chrg=<optimized out>) at ../../../Source/WebCore/loader/PingLoader.cpp:131
#15 0x0000003d939669d2 in WebCore::ThreadTimers::sharedTimerFiredInternal (this=0x7fe9000eb7a8) at ../../../Source/WebCore/platform/ThreadTimers.cpp:112
#16 0x0000003da5191c49 in QObject::event (this=0x16bb9b0, e=<optimized out>) at kernel/qobject.cpp:1157
#17 0x0000003d885c9994 in notify_helper (e=0x7ffff0e8a590, receiver=0x16bb9b0, this=0x11a9290) at kernel/qapplication.cpp:4550
#18 QApplicationPrivate::notify_helper (this=0x11a9290, receiver=0x16bb9b0, e=0x7ffff0e8a590) at kernel/qapplication.cpp:4522
#19 0x0000003d885ce813 in QApplication::notify (this=0x7ffff0e8aa00, receiver=0x16bb9b0, e=0x7ffff0e8a590) at kernel/qapplication.cpp:4411
#20 0x0000003d8a050eb6 in KApplication::notify (this=0x7ffff0e8aa00, receiver=0x16bb9b0, event=0x7ffff0e8a590) at /usr/src/debug/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311
#21 0x0000003da517904c in QCoreApplication::notifyInternal (this=0x7ffff0e8aa00, receiver=0x16bb9b0, event=0x7ffff0e8a590) at kernel/qcoreapplication.cpp:876
#22 0x0000003da51a9b52 in sendEvent (event=0x7ffff0e8a590, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#23 QTimerInfoList::activateTimers (this=0x11ab950) at kernel/qeventdispatcher_unix.cpp:611
#24 0x0000003da51a752d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#25 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#26 0x0000003da51a7551 in idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233
#27 0x0000003d9c844acd in g_main_dispatch (context=0x11abdf0) at gmain.c:2441
#28 g_main_context_dispatch (context=0x11abdf0) at gmain.c:3011
#29 0x0000003d9c8452c8 in g_main_context_iterate (context=0x11abdf0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3089
#30 0x0000003d9c84549c in g_main_context_iteration (context=0x11abdf0, may_block=1) at gmain.c:3152
#31 0x0000003da51a7d5f in QEventDispatcherGlib::processEvents (this=0x117e510, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#32 0x0000003d8866c66e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#33 0x0000003da5178182 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#34 0x0000003da51783d7 in QEventLoop::exec (this=0x7ffff0e8a830, flags=...) at kernel/qeventloop.cpp:204
#35 0x0000003da517cdd5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#36 0x0000003d8d0b5ca2 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#37 0x0000003d9cc2169d in __libc_start_main (main=0x4007c0, argc=2, ubp_av=0x7ffff0e8b2c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff0e8b2b8) at libc-start.c:226
#38 0x00000000004007f1 in _start ()

Find attached a full backtrace at https://bugs.kde.org/show_bug.cgi?id=294707

This is my first webkit reported bug, so maybe this one is lacking information. Feel free to request any information needed to debug the problem.

Thanks and regards,

[Matthew Woehlke]

I experience the same bug (same stack trace) on multiple machines... leaving a konqueror window open with some tabs using webkit to render, after going away for some hours (usually over night) - NOT suspending/hibernating/etc., just leave the computer running - konqueror has crashed when I come back.

[Thomas Tanghus]

Created attachment 180937 [details]
Backtrace from KDE bug assistant

I experience the same bug in Kontact/Akregator when using QtWebkit also when just having it open at idle. Several other reports are at https://bugs.kde.org/show_bug.cgi?id=294707

[Nick Leverton]

Created attachment 207498 [details]
Crash dump under Qt 4.8.2 (Debian Stable)

Is there a fix available for this ?  It is still happening in Debian Stable with Qt 4.8.2.  Afraid I'm not in a position to try Sid with 4.8.5 but any news would be welcome.

[Jan Kundrát]

Looks like a duplicate of https://bugs.webkit.org/show_bug.cgi?id=116035 which is already fixed (but without a release in Qt).

[Alexey Proskuryakov]

The Qt port has been removed from WebKit, resolving this bug.