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

Bug 362613

Summary: Debugger setting freezes Eclipse
Product: [WebTools] JSDT Reporter: msch Mising name <post_msch-bugzilla>
Component: DebugAssignee: Project Inbox <jsdt.debug-inbox>
Status: CLOSED DUPLICATE QA Contact: Michael Rennie <Michael_Rennie>
Severity: critical    
Priority: P3 CC: Michael_Rennie, thatnitind
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Threaddump taken with jvisualvm none

Description msch Mising name CLA 2011-11-01 20:11:20 EDT 
Build Identifier: M20110909-1335

When the Debugger setting "Suspend on JavaScript exceptions" under Window/Preferences/JavaScript/Debug/General Settings is enabled (checked) any file system activity freezes the Eclipse IDE.  Eclipse has to be forced to shut down by Windows task manager.  Furthermore, this default setting cannot be disabled ( see: Bug 362611), so unless after every Eclipse start the user remembers to change that specific setting, Eclipse freezes after a while or after some file system activities.

Reproducible: Always

Steps to Reproduce:
1.Start Eclipse
2.Edit and save a javascript file
3.-> Eclipse freezes.  Force shutdown (Taskmanager or multiple clicks on 'close window icon'.
4. Start Eclipse
5. Disable "Suspend on JavaScript exceptions" under Window/Preferences/JavaScript/Debug/General
6. Edit and save a javascript file.  -> No Problems
Comment 1 Michael Rennie CLA 2011-11-02 10:18:45 EDT 
Can you take a stack dump and add it to the bug?

http://wiki.eclipse.org/How_to_report_a_deadlock
Comment 2 msch Mising name CLA 2011-11-03 18:41:57 EDT 
Created attachment 206437 [details]
Threaddump taken with jvisualvm

1. Eclipse was started with -Dcom.sun.management.jmxremote in eclipse.ini.  
2. Ctrl+s was pressed -> Freezing of eclipse
3. Thread dump was taken

In another thread dump, taken with "suspend on javascript exception" disabled, the lines 
"Worker-13" prio=6 tid=0x07138800 nid=0xb14 waiting for monitor entry [0x0970e000]
   java.lang.Thread.State: BLOCKED (on object monitor)
were not present (and eclipse did not freeze :-)

By the way, previous attempts of fiddling with XXMaxPermSize, -Xms -Xmx showed no effects on freezing/not freezing.


Content of eclipse.ini:
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
C:/Program Files (x86)/Java/jdk1.7.0/jre/bin/javaw.exe
-vmargs
-Xms40m
-Xmx384m
-Dcom.sun.management.jmxremote
Comment 3 Michael Rennie CLA 2011-11-04 09:28:20 EDT 
(In reply to comment #2)
> Created attachment 206437 [details]
> Threaddump taken with jvisualvm

Thanks for reporting back, this is  dupe of bug 345298 where the breakpoint manager is dead-locking trying to restore breakpoints.

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