| Summary: | [breakpoints] It takes a long time to toggle a breakpoint | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Frederic Fusier <frederic_fusier> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | darin.eclipse, Michael_Rennie |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Frederic Fusier
(In reply to comment #0) > Is it related to the current issue or should I open a new bug for this? > Forgot this sentence, I initially wrote the comment in bug 286938 and finally decide that it was better to directly open a new bug... Mike, can you investigate? Still waiting on the performance tests (locally), but it does seem a bit sluggish toggling a breakpoint in the Scribe class Frederic mentioned. The only fixes that have gone into Debug for breakpoints that would affect toggling are: https://bugs.eclipse.org/bugs/show_bug.cgi?id=208744 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=223315 the second bug makes use of ITypeBindings but cuts down the number of ASTs we used to create by a factor of 4 for line breakpoints (used to create 4 now it only creates 1). investigating... Note that it does not looks related to this specific CU as I also get the same problem with any other smaller or bigger JDT/Core classes, e.g.: - org.eclipse.jdt.core.tests.formatter.FormatterMassiveRegressionTests -> 44,805 bytes: approx. same times than Scribe to set/unset bkp - org.eclipse.jdt.internal.compiler.parser.Parser -> 410,053 bytes: approx. double times than Scribe to set/unset bkp On all tests I did, it seems that the time does not depend on the bkp position (ie. it's the same setting/unsetting bkp at the beginning or at the end of the CU). One more piece of information, I tried with the largest file we have in JDT/Core: org.eclipse.jdt.core.tests.compiler.regression.GenericTypeTest which is 1,732,826 bytes long and it takes the same time than for Scribe. That would mean this time was more dependent on the nodes numbers (or nodes hierarchy complexity) rather than pure file length... HTH 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. If you have further information on the current state of the bug, please add it. 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. |