Bug 113619 - Konqueror crash when clicking on tab with SIG 6
Summary: Konqueror crash when clicking on tab with SIG 6
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: tabbing (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 135715 148672 161546 163360 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-09-30 12:53 UTC by Avuton Olrich
Modified: 2008-12-01 17:58 UTC (History)
5 users (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 Avuton Olrich 2005-09-30 12:53:01 UTC
Version:           3.5 beta1 (using KDE KDE 3.4.90)
Installed from:    Gentoo Packages
Compiler:          GCC 3.4.4-r1 
OS:                Linux

Konqueror crashed when closing a tab. The best way I can explain what happened is I had about 8 tabs open, computer was under a pretty good load, things were running pretty slow, I clicked the 'x' to close the tab then due to the slow reaction of the computer I clicked the 'x' again, probably closing a second tab and then I received this dump:

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1236199760 (LWP 10280)]
[KCrash handler]
#4  0xffffe410 in __kernel_vsyscall ()
#5  0xb653d391 in *__GI_raise (sig=6) at raise.c:64
#6  0xb653edad in *__GI_abort () at abort.c:88
#7  0xb66fd913 in __gnu_cxx::__verbose_terminate_handler ()
    at /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libstdc++-v3/libsupc++/vterminate.cc:96
#8  0xb66fb4c5 in __cxxabiv1::__terminate (
    handler=0xb66fd7a0 <__gnu_cxx::__verbose_terminate_handler()>)
    at /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libstdc++-v3/libsupc++/eh_terminate.cc:43
#9  0xb66fb502 in std::terminate ()
    at /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libstdc++-v3/libsupc++/eh_terminate.cc:53
#10 0xb66fba05 in __cxa_pure_virtual ()
    at /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libstdc++-v3/libsupc++/pure.cc:50
#11 0xb7f3f1b0 in KonqViewManager::removeTab (this=0x8193e88, tab=0xa6f217c)
    at konq_viewmgr.cc:563
#12 0xb7f6804b in KonqMainWindow::slotRemoveTabPopupDelayed (this=0x0)
    at konq_mainwindow.cc:2743
#13 0xb7f8879d in KonqMainWindow::qt_invoke (this=0x818b390, _id=162, 
    _o=0xbfbcd7e0) at konq_mainwindow.moc:681
#14 0xb6d2878a in QObject::activate_signal (this=0x8288598, clist=0xa6331e0, 
    o=0xbfbcd7e0) at qobject.cpp:2355
#15 0xb710baf3 in QSignal::signal (this=0x8288598, t0=@0x82885c0)
    at moc_qsignal.cpp:100
#16 0xb6d4acdd in QSignal::activate (this=0x8288598) at qsignal.cpp:212
#17 0xb6d54e26 in QSingleShotTimer::event (this=0x8288570) at qtimer.cpp:286
#18 0xb6cb7dfd in QApplication::internalNotify (this=0xbfbce070, 
    receiver=0x8288570, e=0xbfbcdb20) at qapplication.cpp:2635
#19 0xb6cb704d in QApplication::notify (this=0xbfbce070, receiver=0x8288570, 
    e=0xbfbcdb20) at qapplication.cpp:2358
#20 0xb7536c5b in KApplication::notify (this=0xbfbce070, receiver=0x8288570, 
    event=0xbfbcdb20) at kapplication.cpp:550
#21 0xb7f3ae74 in QApplication::sendEvent (receiver=0x6, event=0x6)
    at qapplication.h:491
#22 0xb6ca3301 in QEventLoop::activateTimers (this=0x811ede8)
    at qeventloop_unix.cpp:556
#23 0xb6c53566 in QEventLoop::processEvents (this=0x811ede8, flags=4)
    at qeventloop_x11.cpp:389
#24 0xb6ccfd03 in QEventLoop::enterLoop (this=0x811ede8) at qeventloop.cpp:198
#25 0xb6ccfc1e in QEventLoop::exec (this=0x811ede8) at qeventloop.cpp:145
#26 0xb6cb7f91 in QApplication::exec (this=0xbfbce070)
    at qapplication.cpp:2758
#27 0xb7f252fb in kdemain (argc=0, argv=0x0) at konq_main.cc:206
#28 0x080486fe in main (argc=0, argv=0x0) at konqueror.la.cc:2
Comment 1 Tommi Tervo 2005-09-30 13:40:49 UTC
Same happened to me with 3.5 svn a while ago.

#11 0x00c3dc24 in KonqViewManager::removeTab (this=0x9899500, tab=0x9bebadc)
    at konq_viewmgr.cc:563
#12 0x00c6aa33 in KonqMainWindow::slotRemoveTabPopupDelayed (this=0x988fe50)
    at konq_mainwindow.cc:2743
#13 0x00c7ff31 in KonqMainWindow::qt_invoke (this=0x988fe50, _id=163,
    _o=0xbff102d0) at konq_mainwindow.moc:681
#14 0x01411450 in QObject::activate_signal ()
Comment 2 Tommi Tervo 2006-10-16 10:07:52 UTC
*** Bug 135715 has been marked as a duplicate of this bug. ***
Comment 3 Roger Larsson 2006-11-21 20:48:28 UTC
And a similar case for me (was the slotRemoveTabPopupDelayed optimized away?):
Konqueror 3.5.1 (KDE 3.5.1 Level "a" SUSE 10.1)

#10 0x00002b0ef5ed735f in __cxa_pure_virtual () from /usr/lib64/libstdc++.so.6
#11 0x00002b0ef8c10a7d in KonqViewManager::removeTab ()
   from /opt/kde3/lib64/libkdeinit_konqueror.so
#12 0x00002b0ef8c21269 in KonqMainWindow::qt_invoke ()
   from /opt/kde3/lib64/libkdeinit_konqueror.so
#13 0x00002b0ef54fe7ac in QObject::activate_signal ()
Comment 4 Roger Larsson 2006-11-21 21:03:40 UTC
I wonder if this is due to an interaction with gestures.
(The bug report says nothing about when closing a tab, and I do not
think I did that either)

But there is (I have) TWO gesture defined that closes a tab:
Press, move right, move down, move right, release
Press, mowe down, move right, release

This could easily interact with clicking on tabs...
So, getting both a key click to show a tab and a keyboard shortcut to
close it at the same time...

IMHO gestures should be integrated with other shortcuts in the menu
bug:73553
Comment 5 Tommi Tervo 2007-08-23 13:36:20 UTC
*** Bug 148672 has been marked as a duplicate of this bug. ***
Comment 6 Pino Toscano 2008-05-03 10:46:02 UTC
*** Bug 161546 has been marked as a duplicate of this bug. ***
Comment 7 A. Spehr 2008-07-19 04:03:27 UTC
*** Bug 163360 has been marked as a duplicate of this bug. ***
Comment 8 A. Spehr 2008-12-01 11:23:47 UTC
Does anybody have this problem in 3.5.10? 
Comment 9 Oleg Atamanenko 2008-12-01 15:40:40 UTC
I can't reproduce this bug since 3.5.10.
Comment 10 A. Spehr 2008-12-01 17:58:41 UTC
(I haven't either...)

If that changes and somebody hits it somehow, please reopen. 

Thanks!