Bug 167616

Summary: konqueror crashes on closing while hotmail.com opened
Product: [Applications] konqueror Reporter: Dominik Tritscher <dominik.tritscher>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: 4.0.98   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dominik Tritscher 2008-07-28 20:16:57 UTC
Version:            (using KDE 4.0.98)
Installed from:    Ubuntu Packages
OS:                Linux

I had hotmail.com at the inbox-page opened as the only page in konqueror. When closing that konqueror instance it crashed and produced following backtrace:

Application: Konqueror (konqueror), signal SIGABRT
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb60da940 (LWP 16131)]
[KCrash handler]
#6  0xb7fb3410 in __kernel_vsyscall ()
#7  0xb7d95085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7d96a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7d8e10e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb41a1022 in KHTMLGlobal::finalCheck ()
    at /build/buildd/kde4libs-4.0.98a/khtml/khtml_global.cpp:247
#11 0xb45cb1ec in ~KHTMLFactory (this=0x8541308)
    at /build/buildd/kde4libs-4.0.98a/khtml/khtml_factory.cpp:35
#12 0xb74f43cf in QObjectCleanupHandler::clear () from /usr/lib/libQtCore.so.4
#13 0xb74f4440 in QObjectCleanupHandler::~QObjectCleanupHandler ()
   from /usr/lib/libQtCore.so.4
#14 0xb776d2ad in destroy ()
    at /build/buildd/kde4libs-4.0.98a/kdecore/util/kpluginfactory.cpp:29
#15 0xb765bb7b in ~KCleanUpGlobalStatic (this=0xb77a2874)
    at /build/buildd/kde4libs-4.0.98a/kdecore/kernel/kglobal.h:67
#16 0xb7d98084 in exit () from /lib/tls/i686/cmov/libc.so.6
#17 0xb7d80458 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#18 0x080484f1 in _start ()
#0  0xb7fb3410 in __kernel_vsyscall ()
Comment 1 Frank Reininghaus 2008-07-28 21:05:39 UTC
Thanks for the bug report. This looks very much like a duplicate of a bug that has been reported a couple of times already.

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