Community
Participate
Working Groups
Created attachment 199493 [details] stack trace (Control-Break) and installation details Eclipse blocks when switching to the debug perspective with an open Breakpoints view if at least one breakpoint exists. Reproduce the error: start eclipe (indigo) with console and use fresh workspace, e.g. D:\WorkspaceTestJSDTDeadlock Create new JavaScript project via package explorer, e.g. "JavaScriptProject" Create a new JavaScript source file on the new project, e.g. "Source.js" and save it. add an arbitrary line of code to the new script file, e.g. "var hello = 0;" Add a breakpoint to this line (double-click on the bar at the left of the edit window) Switch to the debug perspevctive and open the "Breakpoints" view to make sure that the breakpoint exists. Switch back to JavaScript perspective Exit the session (File -> exit) Restart Eclipse using the same workspace. Switch to the "Debug" perspective. --> eclipse blocks (shows egg timer) Eclipse does no longer block, if the breakpoint is removed. Please find the following information attached below: == stack-dump == installation details / configuration
additional information: The system does NOT seem to block, if the Breakpoints view has been opened once with all JavaScript projects (containing breakpoints?) closed and then openend, i.e. the following sequence does NOT end in a deadlock: Repeat the steps stated in my original report including "Exit the session". (i.e. create a JavaScript project with a single JavaScript file with a breakpoint) Restart the eclipse session. close the JavaScript project switch to the Debug perspective (and open the Breakpoints view if not already open): this works fine now switch back to the JavaScript perspective open the JavaScript project switch back to the Debug perspective: this does still work and the breakpoint is shown in "Breakpoints"
Same trace as bug 345298, seems the BreakpointManager is dead-locking when we try to add a breakpoint. *** This bug has been marked as a duplicate of bug 345298 ***
