Bug 161082 - konqueror crashes on closing a (popup) window
Summary: konqueror crashes on closing a (popup) window
Status: RESOLVED DUPLICATE of bug 145666
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-20 21:06 UTC by Philippe Widmer
Modified: 2008-08-05 22:40 UTC (History)
0 users

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 Philippe Widmer 2008-04-20 21:06:03 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.1.3 
OS:                Linux

doing the same steps as described in #141170 konqueror build trunk r799124 still results in a crash, although this seems to be a different problem as the attached backtrace suggests. After entering the user name and password, a message box appears asking if I want to allow the popup window to be closed. Then konqueror crashes with the following bt:


Application: Konqueror (konqueror), signal SIGABRT
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239206208 (LWP 11234)]
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb653c875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb653e201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6535b6e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb43e156b in khtml::HTMLTokenizer::reset (this=0x913d2d8)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/html/htmltokenizer.cpp:161
#11 0xb43e16e9 in ~HTMLTokenizer (this=0x913d2d8)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/html/htmltokenizer.cpp:1733
#12 0xb4397213 in DOM::DocumentImpl::detach (this=0x8f878a0)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/xml/dom_docimpl.cpp:1341
#13 0xb43433dc in KHTMLPart::clear (this=0x8ee2b80)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/khtml_part.cpp:1413
#14 0xb435368d in ~KHTMLPart (this=0x8ee2b80)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/khtml_part.cpp:513
#15 0xb43436a2 in KHTMLPart::clear (this=0x8e95698)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/khtml_part.cpp:1452
#16 0xb435368d in ~KHTMLPart (this=0x8e95698)
    at /home/kde4dev/kde/src/KDE/kdelibs/khtml/khtml_part.cpp:513
#17 0xb72410c3 in qDeleteInEventHandler (o=0x8e95698)
    at kernel/qobject.cpp:3595
#18 0xb7245aea in QObject::event (this=0x8e95698, e=0x8bfe9b0)
    at kernel/qobject.cpp:1124
#19 0xb692d427 in QApplicationPrivate::notify_helper (this=0x805c860, 
    receiver=0x8e95698, e=0x8bfe9b0) at kernel/qapplication.cpp:3766
#20 0xb692d719 in QApplication::notify (this=0xbfc86a68, receiver=0x8e95698, 
    e=0x8bfe9b0) at kernel/qapplication.cpp:3360
#21 0xb784b0f1 in KApplication::notify (this=0xbfc86a68, receiver=0x8e95698, 
    event=0x8bfe9b0)
    at /home/kde4dev/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#22 0xb7232782 in QCoreApplication::notifyInternal (this=0xbfc86a68, 
    receiver=0x8e95698, event=0x8bfe9b0) at kernel/qcoreapplication.cpp:583
#23 0xb72360df in QCoreApplication::sendEvent (receiver=0x8e95698, 
    event=0x8bfe9b0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 0xb7232c9a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x804b288) at kernel/qcoreapplication.cpp:1195
#25 0xb7232e4b in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qcoreapplication.cpp:1091
#26 0xb7262734 in QCoreApplication::sendPostedEvents ()
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 0xb726174f in postEventSourceDispatch (s=0x805eb10)
    at kernel/qeventdispatcher_glib.cpp:211
#28 0xb63a911c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb63ac55f in ?? () from /usr/lib/libglib-2.0.so.0
#30 0x0805ea90 in ?? ()
#31 0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 A. Spehr 2008-08-05 22:40:18 UTC

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