This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Debugger loads too many classes on startup | ||
|---|---|---|---|
| Product: | debugger | Reporter: | Jaroslav Tulach <jtulach> |
| Component: | Code | Assignee: | issues@debugger <issues> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | Keywords: | PERFORMANCE |
| Priority: | P2 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | TASK | Exception Reporter: | |
| Bug Depends on: | 18290, 28625 | ||
| Bug Blocks: | 21676, 26764 | ||
|
Description
Jaroslav Tulach
2002-03-29 14:38:57 UTC
Not easy to fix. We must deserialize list of breakpoints (it means meny classes from debugger module) wich should be visible in editor. It means that we can not improve our startup is 80% of IDE starts (editor is typically visible after startup). Hanzi, I do not think that all the classes here are loaded just because of deserialization of breakpoint. I would be very thankfull if you could investigate reasons for all the classes. If you believe something is separate (and moreover design) issue, feel free to create a subissue, but please investigate the rest. I can not simply fix it to NB3.4 - we need some changes in openide - see "depends" section. I can not simply fix it to NB3.4 - we need some changes in openide - see "depends" section. =>> NB4.0 Dear Hanz. I understand that some problems are hard to fix but I am sure that some of them are not. Because this is a performance bug I want us to better understand which we can address in 3.4 version and for which of them we have to prepare solution for 4.0 in the architecture. So please evaluate and divide classes listed here into subissues with reasons why they have to be loaded on startup. To express exactly what is in my mind: I am pretty sure that GUIManager$View is not initalized due to deserialization of breakpoints. Grr. I do not see there any simple solution now. There are several problems: 1) we use module install for some registration [Loaded org.netbeans.modules.debugger.DebuggerImpl] [Loaded org.netbeans.modules.debugger.EventsProducer] [Loaded org.netbeans.modules.debugger.support.DebuggerImplSupport] [Loaded org.netbeans.modules.debugger.ConnectSupport] [Loaded org.netbeans.modules.debugger.jpda.JPDADebuggerImpl] [Loaded org.netbeans.modules.debugger.GUIManager$View] [Loaded org.netbeans.modules.debugger.support.View2] [Loaded org.netbeans.modules.debugger.support.View2Support] [Loaded org.netbeans.modules.debugger.Register] [Loaded org.netbeans.modules.debugger.DebuggerCoreImpl] [Loaded org.netbeans.modules.debugger.delegator.DelegatingDebuggerImpl] [Loaded org.netbeans.modules.debugger.CoreBreakpoint$Event] we can move this registration to layers, but not for NB3.4 - we do not have it in plan ;( 2) other classes are loaded when first debugger action is created and isEnabled () action teste if there is some debugger running. not easy to fix too.... 3) but the biggest problem is loading of breakpoints. that is why we can not fix it during regular development. We need mor time for it (at least 3 weeks I think). so => FRE I promise that if we will have time I will look at it. (I will add it to our plan) Target milestone was changed from '3.4' to TBD. Target milestone was changed from '3.4' to TBD. fixed in projects branch Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |