Community
Participate
Working Groups
Build Identifier: 20110916-0149 In my project (~100 eclipse projects, some rather large) when I set a breakpoint, debug the project and the breakpoint is hit, it takes very long time until the breakpoint line is marked in the editor. It is shown in the Debug window, but takes ~20 secs until it is marked in the editor (even when the corresponding code is already shown in the editor) Reproducible: Always
I also have this problem. I'd add this, though: - only the first hit is veeery slow, i.e. the first breakpoint that is hit after you "run in debug mode" your application/your server (if you're debugging a Tomcat instance with WTP) - you can't watch variables, step forward/into, etc. until the code line highlighting has been performed - since the upgrade from Indigo to Juno, the problem got much worse; I would say it was not a problem in Indigo, but it is in Juno I'm working on Windows 7 64-bit with Eclipse Juno 4.2.1 64-bit. A co-worker of mine has the same problem under Linux Debian 32-bit.
Created attachment 245911 [details] slow-breakpoint-hit I've the same problem, attached a JVisualVM snapshot where it takes ~5 seconds to jump to the source line of the breakpoint. Looks like it reading a zip file in thread Worker-4: org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$SourceLookupJob.run() 5.199 ms which seems to send the most time in I think reading the JDK src.zip (I removed all other sources from the build path). I've about 10 jre/jdks installed (last of JDK 6/7/8 in 32 and 64 bit versions). The problem occurs running a simple unit test with Java 7/8 with a breakpoint in a large project. It occurs as mention the first time a breakpoint is hit after launch in debug mode. Using Eclipse IDE for Java Developers Version: Luna Release (4.4.0) Build id: 20140612-0600 (I incorrectly added this comment to https://bugs.eclipse.org/bugs/show_bug.cgi?id=286938 before)
This bug (or at least mine) is a duplicate of https://bugs.eclipse.org/bugs/show_bug.cgi?id=440470
*** This bug has been marked as a duplicate of bug 440470 ***
Hi Michael, how can this bug (reported in 2011 against Juno) be a duplicate of a 2014 bug reported as a regression in Luna against Kepler?
(In reply to Mauro Molinari from comment #5) > Hi Michael, > how can this bug (reported in 2011 against Juno) be a duplicate of a 2014 > bug reported as a regression in Luna against Kepler? My apologies, I was resolving based on Walters comment. Reopening.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
