Bug 263470 - Konqueror Crash using Zimbra
Summary: Konqueror Crash using Zimbra
Status: RESOLVED UPSTREAM
Alias: None
Product: kwebkitpart
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: webkit-devel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-17 21:18 UTC by Steven Sroka
Modified: 2011-04-25 19:54 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Sroka 2011-01-17 21:18:13 UTC
Application: konqueror (4.5.5 (KDE 4.5.5) "release 1")
KDE Platform Version: 4.5.5 (KDE 4.5.5) "release 1"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Clicking the send button to reply to an email on a web email client (mail.uoguelph.ca)

- Custom settings of the application:
Using libkwebkitpart v0.9-8.6, user agent string for this website is Mozilla/5.0 (X11; U; x86_64 Linux; en_US; rv:1.9.2) Gecko/20100115 Firefox/3.6

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

Thread 2 (Thread 0x7fdd33db3710 (LWP 4756)):
#0  0x00007fdd514a923d in nanosleep () from /lib64/libc.so.6
#1  0x00007fdd514a90a8 in sleep () from /lib64/libc.so.6
#2  0x00007fdd48e8a22f in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4
#3  0x00007fdd48e8a2d9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#4  0x00007fdd526e9a4f in start_thread () from /lib64/libpthread.so.0
#5  0x00007fdd514d982d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fdd53d41760 (LWP 4717)):
[KCrash Handler]
#6  0x00007fdd52973436 in fetchAndAddOrdered (this=0x7fdd32be2b40) at ../../src/corelib/arch/qatomic_x86_64.h:164
#7  fetchAndAddAcquire (this=0x7fdd32be2b40) at ../../src/corelib/arch/qatomic_x86_64.h:297
#8  QMutex::lock (this=0x7fdd32be2b40) at thread/qmutex.cpp:158
#9  0x00007fdd52a61c2e in QCoreApplication::postEvent (receiver=0x136fad0, event=0xb28490, priority=0) at kernel/qcoreapplication.cpp:1135
#10 0x00007fdd4930a470 in WebCore::QNetworkReplyHandler::finish() () from /usr/lib64/libQtWebKit.so.4
#11 0x00007fdd4930abe4 in WebCore::QNetworkReplyHandler::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtWebKit.so.4
#12 0x00007fdd52a70509 in QObject::event (this=0xea84b0, e=0xeab8e0) at kernel/qobject.cpp:1248
#13 0x00007fdd51c334d4 in QApplicationPrivate::notify_helper (this=0x6871e0, receiver=0xea84b0, e=0xeab8e0) at kernel/qapplication.cpp:4302
#14 0x00007fdd51c3baca in QApplication::notify (this=<value optimized out>, receiver=0xea84b0, e=0xeab8e0) at kernel/qapplication.cpp:4185
#15 0x00007fdd536c4876 in KApplication::notify (this=0x7fff8aa951d0, receiver=0xea84b0, event=0xeab8e0) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#16 0x00007fdd52a5ee4c in QCoreApplication::notifyInternal (this=0x7fff8aa951d0, receiver=0xea84b0, event=0xeab8e0) at kernel/qcoreapplication.cpp:726
#17 0x00007fdd52a625ba in sendEvent (receiver=0x0, event_type=0, data=0x60f500) at kernel/qcoreapplication.h:215
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60f500) at kernel/qcoreapplication.cpp:1367
#19 0x00007fdd52a87173 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220
#20 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#21 0x00007fdd4e5e7a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fdd4e5e8270 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fdd4e5e8510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fdd52a8767f in QEventDispatcherGlib::processEvents (this=0x616ba0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007fdd51cd414e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007fdd52a5e292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007fdd52a5e495 in QEventLoop::exec (this=0x7fff8aa94fa0, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007fdd52a6288b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#29 0x00007fdd44ca4c5a in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#30 0x00000000004074a9 in launch (argc=2, _name=0x669798 "/usr/bin/konqueror", args=<value optimized out>, cwd=0x0, envc=<value optimized out>, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x6697c4 "linux-a3hp.site;1295294502;734806;2143_TIME2374552") at /usr/src/debug/kdelibs-4.5.5/kinit/kinit.cpp:723
#31 0x0000000000407fc5 in handle_launcher_request (sock=8, who=<value optimized out>) at /usr/src/debug/kdelibs-4.5.5/kinit/kinit.cpp:1215
#32 0x000000000040873a in handle_requests (waitForPid=<value optimized out>) at /usr/src/debug/kdelibs-4.5.5/kinit/kinit.cpp:1408
#33 0x0000000000409390 in main (argc=4, argv=0x7fff8aa96af8, envp=0x7fff8aa96b20) at /usr/src/debug/kdelibs-4.5.5/kinit/kinit.cpp:1892

Possible duplicates by query: bug 245188, bug 237477, bug 237201, bug 236862, bug 236845.

Reported using DrKonqi
Comment 1 Dawit Alemayehu 2011-04-25 19:54:42 UTC
This backtrace looks like an upstream issue. If this is still a problem in the current versions of both KDE (v4.6.2) and kwebkitpart (v1.1) , then please report it in QtWebKit's bug database @ http://trac.webkit.org/wiki/QtWebKitBugs.