Bug 118787 - SIG11 on switching application windows
Summary: SIG11 on switching application windows
Status: RESOLVED DUPLICATE of bug 117677
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
Depends on:
Reported: 2005-12-21 12:49 UTC by Charles Whittington
Modified: 2006-12-13 20:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

code for Main.java (589 bytes, text/plain)
2006-11-07 01:33 UTC, Petr Dudacek
code for Dialog.java (446 bytes, text/plain)
2006-11-07 01:34 UTC, Petr Dudacek

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Whittington 2005-12-21 12:49:09 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs
OS:                Linux

An application running in Java Virtual Machine occasionally gives SIG11 (backtrace below). Afterwards, top bars (with min.max/close on) disappear from all all applications and panel buttons for applications are disabled. Only the top application continues to work. If that is closed, the next one will work until that is closed, etc. Only remedy is to logout and log back in again. It seems to occur when clicking out of a non-modal JDialog box. There may or may not be an error in the application, or in the JVM, but should KDE be susceptible to being crashed this badly by an application?

Charles Whittington

KDE 3.4.2 level b from SuSE 10.0 out of the box, JVM 1.4.2

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1095227424 (LWP 17361)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#3  0x415ce971 in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#4  0xbfcac9e8 in ?? ()
#5  0x081ab998 in ?? ()
#6  0x08145548 in ?? ()
#7  0xbfcac9c8 in ?? ()
#8  0x415ce98d in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#9  0x0819b598 in ?? ()
#10 0x08145548 in ?? ()
#11 0x00000001 in ?? ()
#12 0xbfcaca18 in ?? ()
#13 0x415fe05d in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#14 0x08145548 in ?? ()
#15 0x0000000c in ?? ()
#16 0x08171748 in ?? ()
#17 0x41622c80 in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#18 0x0819dfd0 in ?? ()
#19 0x001a6fd8 in ?? ()
#20 0xbfcaca38 in ?? ()
#21 0x415dcbad in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#22 0x081a6fd8 in ?? ()
#23 0x081a6fd8 in ?? ()
#24 0x00000000 in ?? ()
#25 0x0819c000 in ?? ()
#26 0xbfcaca1c in ?? ()
#27 0xbfcaca10 in ?? ()
#28 0x0819c000 in ?? ()
#29 0x41622c80 in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#30 0x08145548 in ?? ()
#31 0x08145548 in ?? ()
#32 0xbfcaca38 in ?? ()
#33 0x415fe19e in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#34 0x08116e08 in ?? ()
#35 0x08145548 in ?? ()
#36 0x00000001 in ?? ()
#37 0x00000000 in ?? ()
#38 0x08175d08 in ?? ()
#39 0x08175d00 in ?? ()
#40 0xbfcaca78 in ?? ()
#41 0x415fe433 in ?? () from /opt/kde3/lib/libkdeinit_kwin.so
#42 0x08116e08 in ?? ()
#43 0x08145548 in ?? ()
#44 0x00000000 in ?? ()
#45 0xbfcaca84 in ?? ()
#46 0x08175d08 in ?? ()
#47 0x08145548 in ?? ()
#48 0x08116f64 in ?? ()
#49 0x40e01c61 in operator delete () from /usr/lib/libstdc++.so.6
Comment 1 Stephan Kulow 2005-12-21 15:58:45 UTC
can you reproduce that bug? if so, it might be worthwhile to recompile from source
Comment 2 Charles Whittington 2005-12-21 16:32:51 UTC
Sort of. I can get it to happen after repeating a sequence n times, but 
n is variable. The application is available via Java Webstart, but the 
problem occurs in the app setting the user privileges, so I can't really 
give you access to it!!

Is it worth me trying to find a right-up-to-date KDE rpm for SuSE?
Is it debug symbols you are missing? If so, could you give me 
pre-compiled replacements for the relevant modules?
Or something else quick because I don't have a huge amount of time to 
spend on it  ....

Thanks for your help.

Charles Whittington
Comment 3 Harald Krake 2005-12-22 17:15:48 UTC
I'm observing exactly the same with Fedora Core2, Core3, Core4 and 
Suse 10 (KDE 3.4 and 3.5).
Kwin crashes sometimes (not always, i.e. not reproducable) when a Java-Dialog
is closed. It looks like a multi-threading issue, race condition or alike.
However, the crashes occur *only* with JVM 1.5 (tiger) and *not* with 1.4 --
at least this is the case for my java apps.
What can I do to support you in finding the bug?
Do more crash dumps help?
Comment 4 Philip Rodrigues 2005-12-22 22:45:14 UTC
Harald, I expect more backtraces would be useful for the developers, provided that you have a debug-enabled build. You can tell whether your build is debug-enabled by looking at the backtrace: if it looks sparse like the one posted in the report, you probably don't have debug enabled. HTH.
Comment 5 Harald Krake 2005-12-23 10:42:39 UTC
Philip, according to the backtraces I'm definitely running a non-debug build.
I suspect it's most efficient to replace kwin with a single debug enabled
statically linked binary. Can anyone provide such a binary for me? (Suse 10, KDE 3.5). As an alternative, what is the fastest way to build a debug-enabled
kwin (without the whole KDE stuff)? I suspect I need debug-enabled qt- and
kde-libraries too. Where? Quick howto?

@Charles: you don't need to log out and in again. Press ALT-F1, login with
your account and enter "kwin -display :0.0 &" at the shell prompt.
That's still boring, but better than logging in 10 times a day :-(
Comment 6 Charles Whittington 2005-12-23 13:16:58 UTC
1. It never occurred to me that going up to Java 1.5 might be the cause. 
But I have reverted to 1.4.2_10 and the problem looks as if it has gone 
away (difficult to tell because it is not reproducible at will).  Thanks 
so much for that tip Harald.

2. I could not use the "kwin -display :0.0 &" trick very easily because 
one of the effects is that my keyboard is disabled.

3. Can we make progress on a debug-enabled version of the part we feel 
is the culprit? I am not keen on compiling and installing KDE from sources.

4. Should we alert the Java people? But I don't like cross-posting.

Charles Whittington

Harald Krake wrote:

[bugs.kde.org quoted mail]
Comment 7 Harald Krake 2005-12-23 17:24:15 UTC
Charles, I don't think alerting the java people is necessary.
Java 1.5 works fine with Gnome (metacity) and Fluxbox. I'm running
production systems with that config. That's why I know for sure.
I can't switch back to java 1.4 cause I'm already using some important
features of 1.5. In 1.5, Sun changed the window-handling code due to
extensions of the API (e.g. a new method forcing a window to remain always
on top, etc...). I guess, this is why 1.5 is crashing kwin while 1.4 does not.
Anyway, whatever the java low-level code looks like, it should not
crash the window manager.
With a little howto from the KDE-team I can build a debug enabled kwin.
I just don't want to read through tons of docs. In C/C++ there are
so many ways to build an application. 
In Java there's a build.xml and that's it -- hopefully ;-)
Comment 8 Charles Whittington 2005-12-24 12:16:25 UTC
OK. Right you KDE guys, give us a kwin for SuSE 10 with debug symbols, 
or tell us how to quickly, and we will produce the goods for you.

Comment 9 Lubos Lunak 2006-01-05 16:56:04 UTC
You can get matching debuginfo packages from opensuse ftp mirrors, e.g. ftp.linux.cz/pub/linux/opensuse/distribution/SL-10.0-OSS/inst-source/suse/i586 . Debuginfo for kdebase3, kdelibs3 and qt3 should be sufficient for getting a usable backtrace.
Comment 10 Harald Krake 2006-01-10 12:20:07 UTC
thanx for the link.
However, I already upgraded to 3.5.
Can anybody provide the 3.5-rpms?
Or a quick howto ;-)
Comment 11 Lubos Lunak 2006-01-10 16:42:06 UTC
I suppose just replacing SL-10.0-OSS with SL-OSS-factory should give you that, it's the latest alpha version of OpenSUSE.
If you want to compile yourself, just untar kdebase tarball and then "./configure --enable-debug", "make" and "make install".
However, it might be simpler if you first checked bug #119376, bug #117881 and bug #117677 if your problem isn't the same like one of them. The backtrace alone may not be sufficient for fixing the problem, and if you have a reliable(!) way of reproducing the problem it might be much simpler.
Comment 12 Lubos Lunak 2006-09-20 16:49:41 UTC
Waiting for a response.
Comment 13 Petr Dudacek 2006-11-07 01:32:54 UTC
If anyone wants to try, here is a small Java application that crashes kwin on my system almost in every case. See the steps to reproduce below.

My system uses KDE 3.5.2 (Gentoo ebuilds) and Sun's JDK 1.5.0_08-b03 (Gentoo ebuild as well).

The app consists of Main.java and Dialog.java, just put them in a directory, compile with
# javac Main.java
and launch with
# java Main
to open the main JFrame.

Then click on the button several times (10 seems to be enough for me) to open several child JDialogs. Then close these dialogs one after another in random order. Kwin usually crashes after closing the last child dialog but sometimes earlier.

If kwin doesn't crash, close the whole application and try again :)
Comment 14 Petr Dudacek 2006-11-07 01:33:57 UTC
Created attachment 18448 [details]
code for Main.java
Comment 15 Petr Dudacek 2006-11-07 01:34:29 UTC
Created attachment 18449 [details]
code for Dialog.java
Comment 16 Lubos Lunak 2006-11-14 12:32:42 UTC
Comment 17 Lubos Lunak 2006-12-13 20:18:07 UTC

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