Bug 242162 - Using the "Back" Keyboard Shortcut on Twitter Crashes Webkit Konqueror [WebCore::QNetworkReplyHandler::sendResponseIfNeeded, WebCore::QNetworkReplyHandler::finish]
Summary: Using the "Back" Keyboard Shortcut on Twitter Crashes Webkit Konqueror [WebCo...
Status: RESOLVED UPSTREAM
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdewebkit (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: webkit-devel
URL:
Keywords:
: 243745 246957 251155 261349 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-06-19 13:50 UTC by Evan Cofsky
Modified: 2010-12-27 13:21 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (7.19 KB, text/plain)
2010-06-21 08:24 UTC, Evan Cofsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Evan Cofsky 2010-06-19 13:50:34 UTC
Application: konqueror (4.4.2 (KDE 4.4.2))
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
After "following" someone on Twitter, using the "Back" keyboard shortcut seems to consistently crash Konqueror when using the WebKit kpart. I haven't tried with khtml.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fadf0283760 (LWP 4497))]

Thread 4 (Thread 0x7fade039a710 (LWP 4549)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007fade0399aa0 in ?? ()
#2  0x00007fff4bbf1852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x7fadcfdab710 (LWP 4617)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fade5f34ca6 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fade6ef6e80) at ../JavaScriptCore/wtf/FastMalloc.cpp:2299
#2  0x00007fade5f34ce9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7fade6f04f4c) at ../JavaScriptCore/wtf/FastMalloc.cpp:1433
#3  0x00007fadee4db9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#4  0x00007faded28e6cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fadcbb8a710 (LWP 4798)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fadd96ba2a6 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fadd9998220) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2304
#2  0x00007fadd96ba2e9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0x7fadd99a62ec) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1438
#3  0x00007fadee4db9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#4  0x00007faded28e6cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fadf0283760 (LWP 4497)):
[KCrash Handler]
#5  0x00007fade63b1e99 in WebCore::QNetworkReplyHandler::sendResponseIfNeeded (this=0x25a3c20) at platform/network/qt/QNetworkReplyHandler.cpp:334
#6  0x00007fade63b373d in WebCore::QNetworkReplyHandler::finish (this=0x7fff4bb62740) at platform/network/qt/QNetworkReplyHandler.cpp:220
#7  0x00007fade63b3d54 in WebCore::QNetworkReplyHandler::qt_metacall (this=0x25a3c20, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>)
    at .moc/release-shared/moc_QNetworkReplyHandler.cpp:82
#8  0x00007fadee86fd49 in QObject::event (this=0x25a3c20, e=0x44f92d0) at kernel/qobject.cpp:1248
#9  0x00007faded9fc22c in QApplicationPrivate::notify_helper (this=0x12a81f0, receiver=0x25a3c20, e=0x44f92d0) at kernel/qapplication.cpp:4300
#10 0x00007fadeda026fb in QApplication::notify (this=0x7fff4bb63780, receiver=0x25a3c20, e=0x44f92d0) at kernel/qapplication.cpp:4183
#11 0x00007fadeeda7526 in KApplication::notify (this=0x7fff4bb63780, receiver=0x25a3c20, event=0x44f92d0) at ../../kdeui/kernel/kapplication.cpp:302
#12 0x00007fadee86006c in QCoreApplication::notifyInternal (this=0x7fff4bb63780, receiver=0x25a3c20, event=0x44f92d0) at kernel/qcoreapplication.cpp:704
#13 0x00007fadee8627e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1225c30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1225c30) at kernel/qcoreapplication.cpp:1345
#15 0x00007fadee8899d3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#16 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#17 0x00007fade9c428c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007fade9c46748 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007fade9c468fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#20 0x00007fadee889513 in QEventDispatcherGlib::processEvents (this=0x1227140, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#21 0x00007fadedaac46e in QGuiEventDispatcherGlib::processEvents (this=0x7fff4bb62740, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fadee85e992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007fadee85ed6c in QEventLoop::exec (this=0x7fff4bb63480, flags=) at kernel/qeventloop.cpp:201
#24 0x00007fadee862aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#25 0x00007fade38ae076 in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#26 0x00000000004070f3 in launch (argc=2, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=16, envs=<value optimized out>, reset_env=true, tty=0x0, 
    avoid_loops=false, startup_id_str=0x127d56b "0") at ../../kinit/kinit.cpp:717
#27 0x0000000000407cb0 in handle_launcher_request (sock=25, who=<value optimized out>) at ../../kinit/kinit.cpp:1209
#28 0x0000000000408219 in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1393
#29 0x0000000000408e22 in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1845

Reported using DrKonqi
Comment 1 Evan Cofsky 2010-06-21 08:24:49 UTC
Created attachment 48177 [details]
New crash information added by DrKonqi

This time I had been running Konqueror with multiple instances for several hours. I don't believe I hit "Back" immediately before the crash.
Comment 2 Dawit Alemayehu 2010-07-20 17:52:27 UTC
This is an upstream issue. I am however unable to reproduce the crash with QtWebKit 2.0 which will be included with the upcoming Qt 4.7 release. If you still have this issue once Qt 4.7 is released, please open a ticket upstream:

https://trac.webkit.org/wiki/QtWebKitBugs
Comment 3 Dario Andres 2010-11-18 21:24:25 UTC
*** Bug 243745 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2010-11-18 21:24:26 UTC
*** Bug 246957 has been marked as a duplicate of this bug. ***
Comment 5 Dario Andres 2010-11-18 21:25:13 UTC
*** Bug 251155 has been marked as a duplicate of this bug. ***
Comment 6 Dario Andres 2010-12-27 13:21:12 UTC
*** Bug 261349 has been marked as a duplicate of this bug. ***