FULL PRODUCT VERSION :
All (1.4/1.5/1.6ea), previously thought only to happen on 1.5+, behaviour although less frequent also
happens on 1.4.
ADDITIONAL OS VERSION INFORMATION :
SuSE 9.3 Pro
Linux cirque-1 220.127.116.11-21.7-smp #1 SMP Thu Jun 2 14:23:14 UTC 2005 i686 i686 i386 GNU/Linux
A DESCRIPTION OF THE PROBLEM :
JTable editing can cause the entire keyboard subsystem to lock up, only
to be released upon restart of the VM. The rest of the machine keeps working
fine, the java program keeps running "fine" (mouse, focus, .. works), except
that it no longer responds to the keyboard at all.
The problems seems to be related to the SMP kernel of Linux; we haven't
been able (yet) to reproduce it on windows/osx/single kernel of Linux.
This is a duplicate of 479050, but I wanted to mention that we were able to
isolate the problem in a small program that should allow you to reproduce the
I'm attaching a zip file with a sample. We tried to strip as much from it as possible. There's a ant file that builds the example, and then you run it via a simple java -cp "./classes" com.Main
You'll see a gui pop up as in the screenshot. Click the "Toggle Edit" button to start edit mode.
The observed behaviour is: - on windows, mac, linux single processor: no problems, works as expected.
- on linux SMP: after editing for a little while, the entire keyboard locks up. Mouse stays functional, focus keeps changing as expected, application is "alive" (resize works,...), but it simply doesn't react to the keyboard anymore. All you can do is kill the app and restart it.
There's another possibility that it might be triggered via a USB keyboard -- if the linux SMP is not the problem, the USB drivers might be. I can do some more tests in case you can't reproduce it for that.
The problem is that sometimes this gets triggered after 10 seconds, sometimes after 5+ minutes; there seems to be a factor of luck involved.
It may very well be that something in my code is wrong; but in any case, the behaviour is undesirable -- the JVM should never allow to be locked up in this way.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
EXPECTED VERSUS ACTUAL BEHAVIOR :
Even if this would turn out to be a programming error; java should never lock
up the keyboard only to release it upon killing the VM.
No more keyboard.
This bug can be reproduced always.
###@###.### 2005-07-20 11:50:26 GMT