Bug 177711

Summary: Konqueror crashes when closing
Product: [Applications] konqueror Reporter: msnkipa
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description msnkipa 2008-12-13 21:04:40 UTC
Version:            (using Devel)
Installed from:    Compiled sources

After I click the "x" button in widow title, and quit konqueror (with one or mode tabs) it`s crashes aftes it`s window has dissapeared.

Backtrace:

Application: Konqueror (konqueror), signal SIGABRT
[?1034h[Thread debugging using libthread_db enabled]
0x00007f638dd80ce1 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f6393402750 (LWP 4481))]

Thread 2 (Thread 0x7f637b086950 (LWP 5057)):
#0  0x00007f638ddab642 in select () from /lib64/libc.so.6
#1  0x00007f63907b0366 in ?? () from /usr/lib64/libQtCore.so.4
#2  0x00007f63906e7f72 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00007f6390474070 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f638ddb20ed in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6393402750 (LWP 4481)):
[KCrash Handler]
#5  0x00007f638dd11645 in raise () from /lib64/libc.so.6
#6  0x00007f638dd12c33 in abort () from /lib64/libc.so.6
#7  0x00007f638dd0a329 in __assert_fail () from /lib64/libc.so.6
#8  0x00007f638445897c in KHTMLGlobal::finalCheck () at /home/kde-devel/kde/src/KDE/kdelibs/khtml/khtml_global.cpp:258
#9  0x00007f63805d8804 in ~KHTMLFactory (this=0xd26d80) at /home/kde-devel/kde/src/KDE/kdelibs/khtml/khtml_factory.cpp:35
#10 0x00007f6390f10c67 in destroy () at /usr/include/QtCore/qalgorithms.h:346
#11 0x00007f638dd142ed in exit () from /lib64/libc.so.6
#12 0x00007f638dcfd58d in __libc_start_main () from /lib64/libc.so.6
#13 0x0000000000400839 in _start () at ../sysdeps/x86_64/elf/start.S:113
Comment 1 Tommi Tervo 2008-12-13 21:06:23 UTC

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