Bug 207485

Summary: Konqueror crashes(SIGABRT) on exit
Product: [Applications] konqueror Reporter: boris64 <bugs.kde>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:

Description boris64 2009-09-15 19:01:47 UTC
Application that crashed: konqueror
Version of the application: 4.3.1 (KDE 4.3.1)
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-2k9-gcc441-04023-g133309a-dirty x86_64

What I was doing when the application crashed:
1) Visit http://www.preisroboter.de/ergebnis2406981.html (no other tabs opened)
2) Exit Konqueror
---> Konqueror crashes with SIGABRT

Reproducible (at least for me).

 -- Backtrace:
Application: Konqueror (konqueror), signal: Aborted
[KCrash Handler]
#5  0x0000003b46832095 in raise () from /lib/libc.so.6
#6  0x0000003b468334c0 in abort () from /lib/libc.so.6
#7  0x0000003b4682b11a in __assert_fail () from /lib/libc.so.6
#8  0x000000352ea2004b in KHTMLGlobal::finalCheck () at /tmp/portage/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1/khtml/khtml_global.cpp:258
#9  0x00007f06790b95aa in ~KHTMLFactory (this=0x1f94aa0) at /tmp/portage/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1/khtml/khtml_factory.cpp:35
#10 0x00000030043534da in QObjectCleanupHandler::clear (this=<value optimized out>) at kernel/qobjectcleanuphandler.cpp:140
#11 0x0000003004353537 in ~QObjectCleanupHandler (this=<value optimized out>) at kernel/qobjectcleanuphandler.cpp:86
#12 0x0000003b46834b35 in __run_exit_handlers () from /lib/libc.so.6
#13 0x0000003b46834b85 in exit () from /lib/libc.so.6
#14 0x0000003b4681ea44 in __libc_start_main () from /lib/libc.so.6
#15 0x00000000004006d9 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-16 03:53:57 UTC
- Does Konqueror crash again if you repeat the steps you described ?
Merging with bug 151453. 
Thanks

*** This bug has been marked as a duplicate of bug 151453 ***
Comment 2 boris64 2009-09-16 04:03:08 UTC
Yeah, happens all the time :/
Comment 3 Dario Andres 2009-09-16 21:02:03 UTC
Mh, can't reproduce here on 4.4 trunk