Bug 190483 - kile 2.1 frequent crash in ubuntu 9.04: "the application kile crashed and caused the signal 11 (SIGSEGV)"
Summary: kile 2.1 frequent crash in ubuntu 9.04: "the application kile crashed and cau...
Status: RESOLVED FIXED
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
: 190912 194696 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-24 01:32 UTC by li tai fang
Modified: 2009-08-20 00:28 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kile backtrace new (2.10 KB, text/plain)
2009-05-03 17:01 UTC, Dhiraj Kumar Hazra
Details

Note You need to log in before you can comment on or make changes to this bug.
Description li tai fang 2009-04-24 01:32:47 UTC
Version:           2.1 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

It occurs with regular frequency in my newly installed Ububtu 9.04. The version is Kile 2.1:


The application kile (Kile) crashed and caused the signal 11 (SIGSEGV).

Application: Kile (kile), signal SIGSEGV
0x00007fe459d1ad21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 8300)]


Thread 2 (Thread 0x7fe448f14950 (LWP 8301)):
#0  0x00007fe459d51742 in select () from /lib/libc.so.6
#1  0x00007fe45a8c2f06 in ?? () from /usr/lib/libQtCore.so.4
#2  0x00007fe45a7fb952 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007fe45770b3ba in start_thread () from /lib/libpthread.so.0
#4  0x00007fe459d58fcd in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe45ebb8750 (LWP 8300)):
[KCrash Handler]
#5  0x00007fe45b4c73b0 in QStackedLayout::currentWidget () from /usr/lib/libQtGui.so.4
#6  0x0000000000680f0d in _start ()
Comment 1 Thomas Braun 2009-04-24 22:04:25 UTC
Can you please give some more information?
What have you done to get the crash?
Can you properly reproduce it?
And a real version number like the one from "apt-cache policy" would be nice too.
Comment 2 Thomas Braun 2009-04-25 00:09:36 UTC
SVN commit 958882 by tbraun:

hopefully fix at least one of the bugs ...
The m_stop action in the manager might not always be a valid pointer, therefore check before dereferencing it.

CCBUG: 190483
CCBUG: 190326


 M  +1 -1      kile.cpp  
 M  +11 -3     kiletoolmanager.cpp  
 M  +3 -0      kiletoolmanager.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=958882
Comment 3 Dhiraj Kumar Hazra 2009-04-26 10:04:09 UTC
I had produced one crash in mandriva.May be related to this bug.
The way I could reproduce the bug is by dragging down a tab like forward dvi and it crashed  after closing kile.
https://qa.mandriva.com/show_bug.cgi?id=49645
Comment 4 li tai fang 2009-04-26 10:16:38 UTC
One thing I've noticed is that, almost every time after I quit the problem, although the timing may be random, the same "Signal 11" message will show up indicating that Kile has crashed. 
The crash message may occur almost immediately after quitting the problem, or sometimes up to 10 minutes after quitting the problem. 

I've downloaded the experimental version here: 
https://launchpad.net/~andreas-wenning/+archive/experimental

I haven't tested it *extensively* yet. It *seems* to crash less, but it still crashes quite regularly.
Comment 5 li tai fang 2009-04-26 10:21:19 UTC
So I tried the "ForwardDVI tab" and then quit Kile.
Sometimes, it crashes immediately after I quit Kile.
Other times, it does not crash immediately after quitting Kile, rather, it crashes the next time I try to open Kile.
Comment 6 li tai fang 2009-04-26 10:31:02 UTC
Actually, the "crash the next time I try to open Kile" issue exists regardless whether I tried to drag down the ForwardDVI or not. The "Signal 11" crash occurs quite randomly, and I'm kinda befuddled. 
By the way, I'm using the 64-bit Ubuntu.
Comment 7 Dhiraj Kumar Hazra 2009-04-26 11:00:01 UTC
I have to check the latest version of kile available in mandriva.The crash while opening I haven't noticed.May be this happens in ubuntu.I will check in ubuntu64 too.
thanks
Comment 8 li tai fang 2009-04-27 10:54:01 UTC
Some interesting info here:

I've been working on the experimental version of Kile a few times now. It does not crash when it's open. All the crashes occur after I quit Kile, although the timing is random. 
Here is the thing: after I quit file, "pgrep kile" STILL yields a process ID, UNTIL the Signal 11 crash. 
Somehow the quitting of Kile isn't quitting completely.

I've tried to open and quit Kile a few times now, and each time Kile "pgrep kile" will yield a process ID after the attempted quit... until the Signal 11 Crash message.
Comment 9 Michel Ludwig 2009-04-28 14:56:05 UTC
*** Bug 190912 has been marked as a duplicate of this bug. ***
Comment 10 Tornio 2009-04-28 19:33:48 UTC
Kile version: 2.1
KDE version: 4.2.2

This is the backtrace:

Applicazione: Kile (kile), segnale SIGSEGV
[Current thread is 0 (LWP 8972)]

Thread 2 (Thread 0xb3815b90 (LWP 8973)):
#0  0xb806d430 in __kernel_vsyscall ()
#1  0xb5f517b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6225380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb615396e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb5b594ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5f5949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5733700 (LWP 8972)):
[KCrash Handler]
#6  0xb6bbb115 in QStackedWidget::currentWidget () from /usr/lib/libQtGui.so.4
#7  0xb6bcb056 in QTabWidget::currentWidget () from /usr/lib/libQtGui.so.4
#8  0x082964d4 in _start ()
Comment 11 Thomas Braun 2009-04-28 20:24:43 UTC
@tornio: You are also on ubuntu? And can you give your Qt version.
Comment 12 David LeBauer 2009-05-02 04:57:23 UTC
I had the same bug after closing Kile 2.1 in Ubuntu 9.04 using alt+F4
I can not reproduce it right now but it has happened a few times
Here are the details :

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
.....(note: above line repeated >30 times)...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5657700 (LWP 8200)]
[New Thread 0xb3709b90 (LWP 8203)]
0xb7f95430 in __kernel_vsyscall ()
[Current thread is 0 (LWP 8200)]

Thread 2 (Thread 0xb3709b90 (LWP 8203)):
#0  0xb7f95430 in __kernel_vsyscall ()
#1  0xb5e757b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6149380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb607796e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb5a7d4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5e7d49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5657700 (LWP 8200)):
#0  0xb7f95430 in __kernel_vsyscall ()
#1  0xb5e387a6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5e385be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb71708b2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7171274 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb685dc12 in ?? () from /usr/lib/libQtGui.so.4
#7  0xb6856c46 in ?? () from /usr/lib/libQtGui.so.4
#8  0xb668a0f6 in QWidgetPrivate::deleteExtra () from /usr/lib/libQtGui.so.4
#9  0xb668a8d5 in QWidgetPrivate::~QWidgetPrivate () from /usr/lib/libQtGui.so.4
#10 0xb6abeaaa in ?? () from /usr/lib/libQtGui.so.4
#11 0xb61832e1 in QObject::~QObject () from /usr/lib/libQtCore.so.4
#12 0xb668f8df in QWidget::~QWidget () from /usr/lib/libQtGui.so.4
#13 0xb6ab3bfd in QMenu::~QMenu () from /usr/lib/libQtGui.so.4
#14 0xb71e7cbf in KMenu::~KMenu () from /usr/lib/libkdeui.so.5
#15 0xb7029bda in KSelectAction::~KSelectAction () from /usr/lib/libkdeui.so.5
#16 0x081b4768 in _start ()
#0  0xb7f95430 in __kernel_vsyscall ()
Comment 13 li tai fang 2009-05-02 08:48:22 UTC
David LeBauer, I've gotten that same message as well, not always reproducible though.
Comment 14 Tornio 2009-05-02 10:10:47 UTC
I have the Kubuntu 9.04 and I have seen that at the next restart of KDE Kile is opened if it had crashed in the session before.
Comment 15 Michel Ludwig 2009-05-03 11:37:50 UTC
There seem to be different crashes mentioned in this bug report.

I can reproduce "one" crash whenever I have changed one of the tools in the tool bar, i.e. I changed ForwardDVI to ViewDVI, and then quit Kile.

Is this also what some of you guys are experiencing?
Comment 16 Dhiraj Kumar Hazra 2009-05-03 12:40:42 UTC
(In reply to comment #15)
> There seem to be different crashes mentioned in this bug report.
> 
> I can reproduce "one" crash whenever I have changed one of the tools in the
> tool bar, i.e. I changed ForwardDVI to ViewDVI, and then quit Kile.
> 
> Is this also what some of you guys are experiencing?
please check although I use mandriva but it looks upstream.You donty need to change the  ForwardDVI to ViewDVI, just drag down any of the toolbars and it crashes
https://qa.mandriva.com/show_bug.cgi?id=49645
Comment 17 Dhiraj Kumar Hazra 2009-05-03 12:42:19 UTC
my backtrace
----------------------------------------------------------
Application: Kile (kile), signal SIGSEGV
[Current thread is 1 (Thread 0xb56308e0 (LWP 29786))]

Thread 2 (Thread 0xb349db90 (LWP 29808)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb62094c1 in select () from /lib/i686/libc.so.6
#2  0xb6eba3fc in QProcessManager::run (this=0x8513350) at io/qprocess_unix.cpp:305
#3  0xb6de24df in QThreadPrivate::start (arg=0x8513350) at thread/qthread_unix.cpp:189
#4  0xb6d85315 in start_thread () from /lib/i686/libpthread.so.0
#5  0xb621125e in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb56308e0 (LWP 29786)):
[KCrash Handler]
#6  0xb66c4c93 in ~QX11WindowSurface (this=0x935d058) at painting/qwindowsurface_x11.cpp:84
#7  0xb66bda54 in ~QWidgetBackingStore (this=0x8c25450) at painting/qbackingstore.cpp:828
#8  0xb64e1dd6 in QWidgetPrivate::deleteExtra (this=0x8e1c8f0) at kernel/qwidget.cpp:1503
#9  0xb64e2583 in ~QWidgetPrivate (this=0x8e1c8f0) at kernel/qwidget.cpp:224
#10 0xb693ae27 in ~QMenuPrivate (this=0x8e1c8f0) at widgets/qmenu_p.h:151
#11 0xb6ef6487 in ~QObject (this=0x8e19de8) at kernel/qobject.cpp:865
#12 0xb64e78a4 in ~QWidget (this=0x8e19de8) at kernel/qwidget.cpp:1386
#13 0xb692fc0c in ~QMenu (this=0x8e19de8) at widgets/qmenu.cpp:1373
#14 0xb75487df in ~KMenu (this=0x8e19de8) at /usr/src/debug/kdelibs-4.2.2/kdeui/widgets/kmenu.cpp:173
#15 0xb7386f1a in ~KSelectAction (this=0x8e1c480) at /usr/src/debug/kdelibs-4.2.2/kdeui/actions/kselectaction.cpp:100
#16 0x08104f76 in ~ToolbarSelectAction (this=0x8e1c480) at /usr/src/debug/kile/src/kileactions.h:205
#17 0xb6eedca4 in QObjectPrivate::deleteChildren (this=0x85104c0) at kernel/qobject.cpp:1845
#18 0xb6ef63dd in ~QObject (this=0xbf97773c) at kernel/qobject.cpp:844
#19 0xb6ee01d4 in ~QCoreApplication (this=0xbf97773c) at kernel/qcoreapplication.cpp:529
#20 0xb649ee35 in ~QApplication (this=0xbf97773c) at kernel/qapplication.cpp:1089
#21 0xb7460518 in ~KApplication (this=0xbf97773c) at /usr/src/debug/kdelibs-4.2.2/kdeui/kernel/kapplication.cpp:928
#22 0x080f77dc in ~Kile (this=0xbf97773c) at /usr/src/debug/kile/src/kile.cpp:310
#23 0x080ff38b in main (argc=2, argv=0xbf977c94) at /usr/src/debug/kile/src/main.cpp:115
Comment 18 Dhiraj Kumar Hazra 2009-05-03 12:44:27 UTC
(In reply to comment #12)
Do you have all the debugging packages installed(including kile-debug)?
Comment 19 Michel Ludwig 2009-05-03 12:59:34 UTC
(In reply to comment #16)
> please check although I use mandriva but it looks upstream.You donty need to
> change the  ForwardDVI to ViewDVI, just drag down any of the toolbars and it
> crashes


Ok, I can confirm that. Clicking the "down arrow" (so that the popup menu expands) on one of the tool select actions is sufficient to trigger the crash when Kile is subsequently closed.
Comment 20 Thomas Braun 2009-05-03 15:00:33 UTC
SVN commit 962890 by tbraun:

disable tool drop down lists if no document is open.
This should fix mandriva #49645.

CCBUG: 190483


 M  +3 -1      kile.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=962890
Comment 21 Thomas Braun 2009-05-03 15:30:27 UTC
So the easy one should be fixed now. This is the one from #19 which Michel described.

The other desribed here should be the same as https://bugs.launchpad.net/bugs/357016. I'm trying to reproduce it here on debian and kubuntu.
Comment 22 Dhiraj Kumar Hazra 2009-05-03 16:54:37 UTC
(In reply to comment #20)
> SVN commit 962890 by tbraun:
> 
> disable tool drop down lists if no document is open.
> This should fix mandriva #49645.
I have tried with opening a tex document .Still the crash happens
after clicking drop down menu.adding a new backtrace.
Comment 23 Dhiraj Kumar Hazra 2009-05-03 17:01:06 UTC
Created attachment 33318 [details]
kile backtrace new
Comment 24 Thomas Braun 2009-05-03 17:16:51 UTC
SVN commit 962946 by tbraun:

Don't use this as parent as it crashes then on ubuntu jaunty.
I verified this on kubuntu using QT 4.5.
With debian lenny and qt 4.4.3 it does not crash.

Any explanations why this fix works are very appreciated ;)

BUG: 190326
CCBUG: 190483
CCMAIL: 357016@bugs.launchpad.net


 M  +4 -4      kile.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=962946
Comment 25 Dario Andres 2009-05-30 23:49:21 UTC
*** Bug 194696 has been marked as a duplicate of this bug. ***
Comment 26 cocoliso 2009-06-15 04:27:18 UTC
I got this in my laptop, I have the upgrated version of ubuntu 9.04 but as far as I see it is a bit different from what all of you have discussed. Since i am not an expert in computers, I would appreciate if someone can tell me if the bug I get is the same as the reported one here. Here is what appears in my screen after I closed Kile


Application: Kile (kile), signal SIGSEGV
[Current thread is 0 (LWP 20553)]

Thread 2 (Thread 0xb2ff8b90 (LWP 20557)):
#0  0xb8024430 in __kernel_vsyscall ()
#1  0xb5f087b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb61dc380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb610a96e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb5b104ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5f1049e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb56ea700 (LWP 20553)):
[KCrash Handler]
#6  0xb6b71d25 in QStackedWidget::currentWidget () from /usr/lib/libQtGui.so.4
#7  0xb6b81c66 in QTabWidget::currentWidget () from /usr/lib/libQtGui.so.4
#8  0x082964d4 in _start ()
Comment 27 pierre.daye 2009-07-17 07:06:32 UTC
Here is my backtrace:

Application: Kile (kile), signal SIGSEGV
0x00007fb415cfed21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 17659)]

Thread 2 (Thread 0x7fb404ebb950 (LWP 17665)):
#0  0x00007fb415d35742 in select () from /lib/libc.so.6
#1  0x00007fb4168997f6 in ?? () from /usr/lib/libQtCore.so.4
#2  0x00007fb4167d1d92 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007fb4136ec3ba in start_thread () from /lib/libpthread.so.0
#4  0x00007fb415d3cfcd in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fb41ab47750 (LWP 17659)):
[KCrash Handler]
#5  0x00007fb41788b8f4 in QTabWidget::currentWidget () from /usr/lib/libQtGui.so.4
#6  0x0000000000680f6d in _start ()
Comment 28 Yves Specht 2009-08-20 00:28:18 UTC
Same problem with Mandriva 2009.1