Bug 320464 - rekonq crashes when the DSL Internet Connection Abruptly Closes
Summary: rekonq crashes when the DSL Internet Connection Abruptly Closes
Status: RESOLVED DUPLICATE of bug 312998
Alias: None
Product: rekonq
Classification: Unmaintained
Component: general (show other bugs)
Version: 2.3.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: qtwebkitToFix
Assignee: Andrea Diamantini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-30 07:10 UTC by Michael
Modified: 2013-06-16 14:37 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (15.38 KB, text/plain)
2013-06-16 10:31 UTC, Benoit Leffray
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2013-05-30 07:10:12 UTC
Application: rekonq (2.3.0)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.9.4-200.fc18.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
on a second pc ( in the same LAN) i have choqok - i close choqok - DSL fucked up.... rekong crashes

-- Backtrace:
Application: rekonq (rekonq), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fe4545a0880 (LWP 1722))]

Thread 6 (Thread 0x7fe449882700 (LWP 1723)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x0000003ab2ea2ab5 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3ab3935a20 <WTF::pageheap_memory>) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:2571
#2  0x0000003ab2ea2b09 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:1767
#3  0x000000346de07d15 in start_thread (arg=0x7fe449882700) at pthread_create.c:308
#4  0x000000346d6f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 5 (Thread 0x7fe408d48700 (LWP 1724)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x0000003ab2be8ce9 in JSC::BlockAllocator::blockFreeingThreadMain (this=0x7fe448fe6398) at /usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x0000003ab2ed123e in WTF::wtfThreadEntryPoint (param=0xe74190) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x000000346de07d15 in start_thread (arg=0x7fe408d48700) at pthread_create.c:308
#4  0x000000346d6f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 4 (Thread 0x7fe403bf6700 (LWP 1725)):
#0  g_main_context_dispatch (context=context@entry=0x7fe3fc0009a0) at gmain.c:3215
#1  0x000000346fe47d88 in g_main_context_iterate (context=context@entry=0x7fe3fc0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290
#2  0x000000346fe47e44 in g_main_context_iteration (context=0x7fe3fc0009a0, may_block=1) at gmain.c:3351
#3  0x0000003477fa5fa6 in QEventDispatcherGlib::processEvents (this=0x7fe3fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x0000003477f765ef in QEventLoop::processEvents (this=this@entry=0x7fe403bf5d00, flags=...) at kernel/qeventloop.cpp:149
#5  0x0000003477f76878 in QEventLoop::exec (this=0x7fe403bf5d00, flags=...) at kernel/qeventloop.cpp:204
#6  0x0000003477e78980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#7  0x0000003477e7b95c in QThreadPrivate::start (arg=0xe14530) at thread/qthread_unix.cpp:338
#8  0x000000346de07d15 in start_thread (arg=0x7fe403bf6700) at pthread_create.c:308
#9  0x000000346d6f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 3 (Thread 0x7fe3c93f3700 (LWP 4567)):
#0  0x000000346d6e99ad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000346fe47d24 in g_main_context_poll (priority=2147483647, n_fds=3, fds=0x7fe3f400ab20, timeout=-1, context=0xbf8ef00) at gmain.c:3584
#2  g_main_context_iterate (context=0xbf8ef00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285
#3  0x000000346fe48182 in g_main_loop_run (loop=0xbf8ee90) at gmain.c:3484
#4  0x000000350facc546 in gdbus_shared_thread_func (user_data=0xbf8eed0) at gdbusprivate.c:277
#5  0x000000346fe6b605 in g_thread_proxy (data=0xbfe7990) at gthread.c:797
#6  0x000000346de07d15 in start_thread (arg=0x7fe3c93f3700) at pthread_create.c:308
#7  0x000000346d6f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 2 (Thread 0x7fe3d3fff700 (LWP 5850)):
#0  g_source_iter_next (iter=iter@entry=0x7fe3d3ffeb20, source=source@entry=0x7fe3d3ffeb18) at gmain.c:874
#1  0x000000346fe47537 in g_main_context_prepare (context=context@entry=0x7fe3ec02cc70, priority=priority@entry=0x7fe3d3ffeb78) at gmain.c:2967
#2  0x000000346fe47c4b in g_main_context_iterate (context=context@entry=0x7fe3ec02cc70, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3270
#3  0x000000346fe47e44 in g_main_context_iteration (context=0x7fe3ec02cc70, may_block=1) at gmain.c:3351
#4  0x0000003477fa5fa6 in QEventDispatcherGlib::processEvents (this=0x7fe3ec02cf70, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x0000003477f765ef in QEventLoop::processEvents (this=this@entry=0x7fe3d3ffecd0, flags=...) at kernel/qeventloop.cpp:149
#6  0x0000003477f76878 in QEventLoop::exec (this=0x7fe3d3ffecd0, flags=...) at kernel/qeventloop.cpp:204
#7  0x0000003477e78980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#8  0x0000003477f56e1f in QInotifyFileSystemWatcherEngine::run (this=0x1e861d0) at io/qfilesystemwatcher_inotify.cpp:256
#9  0x0000003477e7b95c in QThreadPrivate::start (arg=0x1e861d0) at thread/qthread_unix.cpp:338
#10 0x000000346de07d15 in start_thread (arg=0x7fe3d3fff700) at pthread_create.c:308
#11 0x000000346d6f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7fe4545a0880 (LWP 1722)):
[KCrash Handler]
#6  0x0000003477f8f59f in QObject::disconnect (sender=0xbdf0b60, signal=0x0, receiver=0x1d95990, method=0xcc2b069 "receiveMetaData()") at kernel/qobject.cpp:2887
#7  0x0000003ab239c3de in WebCore::QNetworkReplyWrapper::resetConnections () from /lib64/libQtWebKit.so.4
#8  0x0000003ab239c43d in WebCore::QNetworkReplyWrapper::release () from /lib64/libQtWebKit.so.4
#9  0x0000003ab239c5c1 in WebCore::QNetworkReplyHandler::release () from /lib64/libQtWebKit.so.4
#10 0x0000003ab239c61e in WebCore::QNetworkReplyHandler::abort () from /lib64/libQtWebKit.so.4
#11 0x0000003ab23984a9 in WebCore::ResourceHandle::cancel () from /lib64/libQtWebKit.so.4
#12 0x0000003ab2035a22 in WebCore::PingLoader::~PingLoader () from /lib64/libQtWebKit.so.4
#13 0x0000003ab2035ab9 in WebCore::PingLoader::~PingLoader () from /lib64/libQtWebKit.so.4
#14 0x0000003ab2188c4a in WebCore::ThreadTimers::sharedTimerFiredInternal () from /lib64/libQtWebKit.so.4
#15 0x0000003477f8c07c in QObject::event (this=0xe12e30, e=<optimized out>) at kernel/qobject.cpp:1156
#16 0x0000003aa8bca5cc in QApplicationPrivate::notify_helper (this=this@entry=0xc39ff0, receiver=receiver@entry=0xe12e30, e=e@entry=0x7fff6cd36890) at kernel/qapplication.cpp:4562
#17 0x0000003aa8bcea4a in QApplication::notify (this=0x7fff6cd36c50, receiver=0xe12e30, e=0x7fff6cd36890) at kernel/qapplication.cpp:4423
#18 0x0000003aaaa46f16 in KApplication::notify (this=0x7fff6cd36c50, receiver=0xe12e30, event=0x7fff6cd36890) at /usr/src/debug/kdelibs-4.10.3/kdeui/kernel/kapplication.cpp:311
#19 0x0000003477f7793e in QCoreApplication::notifyInternal (this=0x7fff6cd36c50, receiver=0xe12e30, event=0x7fff6cd36890) at kernel/qcoreapplication.cpp:949
#20 0x0000003477fa87f2 in sendEvent (event=0x7fff6cd36890, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#21 QTimerInfoList::activateTimers (this=0xc3eed0) at kernel/qeventdispatcher_unix.cpp:622
#22 0x0000003477fa5914 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#23 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#24 0x0000003477fa5931 in idleTimerSourceDispatch (source=source@entry=0xc3ef20) at kernel/qeventdispatcher_glib.cpp:233
#25 0x000000346fe47a55 in g_main_dispatch (context=0xc37c40) at gmain.c:2715
#26 g_main_context_dispatch (context=context@entry=0xc37c40) at gmain.c:3219
#27 0x000000346fe47d88 in g_main_context_iterate (context=context@entry=0xc37c40, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290
#28 0x000000346fe47e44 in g_main_context_iteration (context=0xc37c40, may_block=1) at gmain.c:3351
#29 0x0000003477fa5f86 in QEventDispatcherGlib::processEvents (this=0xc02aa0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#30 0x0000003aa8c6a73e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#31 0x0000003477f765ef in QEventLoop::processEvents (this=this@entry=0x7fff6cd36b10, flags=...) at kernel/qeventloop.cpp:149
#32 0x0000003477f76878 in QEventLoop::exec (this=0x7fff6cd36b10, flags=...) at kernel/qeventloop.cpp:204
#33 0x0000003477f7b708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#34 0x0000003aae31cc85 in kdemain (argc=1, argv=0x7fff6cd36d98) at /usr/src/debug/rekonq-2.3.0/src/main.cpp:242
#35 0x000000346d621a05 in __libc_start_main (main=0x4008b0 <main(int, char**)>, argc=1, ubp_av=0x7fff6cd36d98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6cd36d88) at libc-start.c:225
#36 0x00000000004008e1 in _start ()

This bug may be a duplicate of or related to bug 318400.

Possible duplicates by query: bug 318400, bug 316443, bug 315618, bug 313002, bug 312998.

Reported using DrKonqi
Comment 1 Shlomi Fish 2013-05-30 11:00:08 UTC
What is DSL in this context? How exactly did the crash happen?
Comment 2 Michael 2013-05-31 11:35:09 UTC
äh, DSL = *D*igital *S*ubscriber *L*ine - this is my uplink to the Net
Comment 3 Michael 2013-05-31 11:36:31 UTC
i dont know how exactly happen...  sorry....
Comment 4 Shlomi Fish 2013-05-31 12:37:01 UTC
So you mean that when you close choqok and the DSL connection abruptly closes, then that confuses rekonq which causes it to crash?

Regards,

-- Shlomi Fish
Comment 5 Michael 2013-06-01 11:15:19 UTC
yes, this is right... ! thanks for your help
Comment 6 Benoit Leffray 2013-06-16 10:31:00 UTC
Created attachment 80546 [details]
New crash information added by DrKonqi

rekonq (2.3.0) on KDE Platform 4.10.4 using Qt 4.8.4

- What I was doing when the application crashed:

I was not doing anything with Rekong at the time it crashed.

-- Backtrace (Reduced):
#6  0x00007fc5a551ce4f in QObject::disconnect (sender=0xa0beed0, signal=0x0, receiver=0x35f8b10, method=0xbfd4509 "receiveMetaData()") at kernel/qobject.cpp:2887
#7  0x00007fc5a994a54e in WebCore::QNetworkReplyWrapper::resetConnections() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#8  0x00007fc5a994a5ad in WebCore::QNetworkReplyWrapper::release() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#9  0x00007fc5a994a731 in WebCore::QNetworkReplyHandler::release() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#10 0x00007fc5a994a78e in WebCore::QNetworkReplyHandler::abort() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
Comment 7 Andrea Diamantini 2013-06-16 14:37:26 UTC

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