Community
Participate
Working Groups
Build Identifier: I20100909-0800 I get freezes a few seconds into the main screen of Eclipse. I was not able to get solve it by closing projects etc (because I never get that far). New workspaces work for a few hours, or at least until I create a web project (which is the work I'm trying to get done anyways). I think this is bug #345298 in the flesh, but on an earlier 3.6.1 version, and more critical than reported there. It actually has become an absolute showstopper for me. My threaddump has a similar stacktrace. I haven't seen the debug or bookmarks-related behavior, so I'm not sure what exactly triggers it. It might be that Aptana Web Studio 3 always runs this broken code, whereas other perspectives only do this now and then, which is why I have more problems with it. In the beginning I suspected the Scala IDE (as I was trying to remove plugins I seemingly couldn't get that one uninstalled properly), but I think I was wrong there: http://www.assembla.com/spaces/scala-ide/tickets/1000759 I have no idea how I could get the fix on 3.6.1, but god knows I need one. This is a Gentoo source build of eclipse and therefore hard to fix (3.6 is latest stable, hard and long to build, might lose plugins on rebuild). Reproducible: Always Steps to Reproduce: 1.Create a new workspace and work with it for a while. Creating an Aptana Web Studio 3 Web project from a template particularly seems to trigger the behavior. From that moment on it will always reproduce, until you create a new workspace. But it happens very quick, so Eclipse is practically rendered useless. 2. Start eclipse. 3. After a few seconds into the main screen it will freeze (it's already done doing visible background work). You won't have time to close projects or otherwise. The problem seems to be especially present when using Aptana Web Studio 3, and when opening the web perspective. I did use to have a bit more time until freeze when using the Java/Android perspective.
Created attachment 207767 [details] threaddump My threaddump. Notice the BLOCKED near breakpointmanager.
Did I write "bookmarks"? I meant "breakpoints" of course.
Thanks for the stack-dump and steps pjv! Marking as a dupe of 345298. Once that fix has been in a few builds and really stress-tested, we can discuss back-porting it to earlier versions. *** This bug has been marked as a duplicate of bug 345298 ***
Since that might take a long time, is there a workaround that allows me to erase breakpoints, or why am I seeing this now and not before?
(In reply to comment #4) > Since that might take a long time, It won't be very long, we are just focusing on getting M4 out the door. So I would say at the most 1 week for the back-porting to be done. > is there a workaround that allows me to > erase breakpoints, or why am I seeing this now and not before? The simplest workaround is to update to this weeks I-build or last weeks 3.7.2 build. The hard way is to delete the breakpoints, which involves removing all markers from your workspace (since breakpoint infos are stored along with their marker infos). The file to delete can be found: <path_to_your_workspace>.metadata\.plugins\org.eclipse.core.resources\.root\.markers I would caution you though that removing the .markers file will remove all of the markers from your workspace. Then you would want to make sure that the setting in JSDT to try and create error / script load breakpoints is off. To do that go to: <path_to_your_workspace>\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.wst.jsdt.debug.core.prefs and set the two preferences to false: org.eclipse.wst.jsdt.debug.core.suspend_on_all_script_loads=false org.eclipse.wst.jsdt.debug.core.suspend_on_thrown_exceptions=false
Thanks, the workaround seems to hold.
