Community
Participate
Working Groups
I'm stopped at a breakpoint and click on a stack frame to edit its source code. Then I click on another stack frame and there is a noticable pause before I can see that code. Click on the first one again, noticable pause. I profiled this and most of the time is spent under the routines CompilationUnit.becomeWorkingCopy and CompilationUnit.discardWorkingCopy. See the attached output from Yourkit for details. The two java source files I'm switching between are 2792 and 251 lines long, respectively (BuiltinFunTable and FunCall from mondrian sourceforge project if it matters). Both are in my workspace (not being pulled from Jars). They are not dirty. I have advanced formatting and annotations turned on but the tracebacks are not implicating those that I can see. I notice some slowness with other files but this is the only case I looked at in detail. JVM mem size is set to 256MB.
Created attachment 13689 [details] Compressed .cpu sample from YourKit 3.0 eap build 401 To get this I turned on sampling and switched back and forth between the two files a few times in the debug view, then turned off sampling. I did NOT have the outline view open.
Do you get similar behaviour outside of the debugger (ie. in the Java perspective) with the same 2 files?
According to the attached cpu sample, 49% of the time is spent in og.eclipse.debug.internal.core.OutputStreamMonitor$1.run(). Only 4% of the time is spent in becomeWorkingCopy. Moving to JDT Debug for comment.
OutputStreamMonitor has undergone significant changes as part of the console reworking in 3.1. Is this still an issue?
Created attachment 16707 [details] Updated compressed .cpu trace file I still see slowness here. I captured a new cpu log with YourKit3.2, Method tracing enabled, JDK5, and the I20041214-2000 build of Eclipse 3.1.
Re comment #2: No, if both files are open side-by-side I don't get any slowness in any case. It's only if there is one editor window and I'm in the debug view and the IDE is swapping the contents of the editor window for another file because I clicked on the stack trace.
Sorry, I only have version 2.5.2 of yourkit. Does the trace look like a problem with the debugger, or a problem with the editor framework for resetting the input?
Not seeing the slowness. Marking as WORKSFORME