Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 291994

Summary: When the debugger hits a particular breakpoint, x windows freezes
Product: [Eclipse Project] JDT Reporter: Michael Fairbank <michael.fairbank>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: Michael_Rennie, remy.suen
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
An eclipse sample project that causes the bug to occur. none

Description Michael Fairbank CLA 2009-10-11 07:25:19 EDT 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.14) Gecko/2009090217 Ubuntu/9.04 (jaunty) Firefox/3.0.14
Build Identifier: 20090920-1017

Follow the steps to reproduce detailed below, which makes GNOME/Eclipse/X-Windows hang.  When the debugger hits a certain line of the project attached, the crash occurs.  The symptoms are that the mouse pointer still moves, but no window will open, move, minimise or respond in anyway.  The system monitor CPU usage graph continues though despite the crash.

I am using the following operating system with java version and IDE: 

Ubuntu AMD 64bit (Release 9.04 (jaunty), Kernel Linux 2.6.28-15-generic, GNOME 2.26.1), 

Java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)

Eclipse IDE for Java Developers  Build id: 20090920-1017

Reproducible: Always

Steps to Reproduce:
Import the attached project into eclipse (use "import existing projects" option of eclipse). 

Make sure there is a breakpoint on line 45 of MainClass.java (this line reads "((PluggableOptimiser) tralgGradDescRegular).useNewOptimiser(opt);")

Run MainClass.java in debug mode through eclipse IDE.

The application should display a "drop down" or combo-box.  Select item B in the combo box.

The debugger should pause at the breakpoint, but at this point X windows freezes completely.  The only way I could continue was to switch the computer off and reboot.  It happens every time.

I'm not sure if the bug is with Eclipse, Java or Ubuntu/Gnome that I'm using.
Comment 1 Michael Fairbank CLA 2009-10-11 07:27:43 EDT 
Created attachment 149316 [details]
An eclipse sample project that causes the bug to occur.
Comment 2 Remy Suen CLA 2009-10-11 09:21:07 EDT 
Reproduced with Sun's 1.6.0.14 JDK. Cannot reproduce with 1.5.0.17. I suspect this to be a JVM problem.
Comment 3 Remy Suen CLA 2009-10-11 09:25:17 EDT 
(In reply to comment #0)
> The debugger should pause at the breakpoint, but at this point X windows
> freezes completely.  The only way I could continue was to switch the computer
> off and reboot.

I just switched to another tty away from X and killed the debugged Java process. Switching back to X afterwards gave me control again.
Comment 4 Michael Fairbank CLA 2009-10-11 13:49:58 EDT 
(In reply to comment #2)
> Reproduced with Sun's 1.6.0.14 JDK. Cannot reproduce with 1.5.0.17. I suspect
> this to be a JVM problem.

Thanks for looking at it.  I first found the bug with java 1.6.0.12, and then I upgraded to 1.6.0.16 and found the bug still happening.  The latest java currently available on http://java.sun.com/javase/downloads/index.jsp is version 1.6.0.16.  Where can I get 1.6.0.17?

Thanks again.
Comment 5 Michael Fairbank CLA 2009-10-11 14:21:04 EDT 
(In reply to comment #4)
> (In reply to comment #2)
> > Reproduced with Sun's 1.6.0.14 JDK. Cannot reproduce with 1.5.0.17. I suspect
> > this to be a JVM problem.
> 
> Thanks for looking at it.  I first found the bug with java 1.6.0.12, and then I
> upgraded to 1.6.0.16 and found the bug still happening.  The latest java
> currently available on http://java.sun.com/javase/downloads/index.jsp is
> version 1.6.0.16.  Where can I get 1.6.0.17?
> 
> Thanks again.

Ok I see you used 1.5 not 1.6, and I've found where I can get development versions of the very latest versions of JDK.
Comment 6 Michael Rennie CLA 2009-10-13 11:04:38 EDT 

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