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.
The use of DebuggerWarmUpTask for breakpoint deserialization is wrong and needs to be avoided. First of all the whole idea of deserialization of all breakpoints during startup sequence is bad. It seems to be deficiency of our APIs that it cannot be done lazily. Now we have moved them to warmup but the semantic of warm up does not guarantee when they will be processed and causes strange behaviour when they are displayed randomly after startup. Growing warmup also affects user perception of application behaviour. Though it looks started it is not fully responsive and a lot of processing is still done before warmup is processed.
Persistence of breakpoints is yet to be designed for the new release.
fixed in the main trunk! RCS file: /cvs/debuggerjpda/ui/src/META-INF/services/org.openide.text.AnnotationProvider,v done Checking in ui/src/META-INF/services/org.openide.text.AnnotationProvider; /cvs/debuggerjpda/ui/src/META-INF/services/org.openide.text.AnnotationProvider,v <-- org.openide.text.AnnotationProvider initial revision: 1.1 done Processing log script arguments... More commits to come... RCS file: /cvs/debuggerjpda/ui/src/org/netbeans/modules/debugger/jpda/ui/BreakpointAnnotationProvider.java,v done Checking in ui/src/org/netbeans/modules/debugger/jpda/ui/BreakpointAnnotationProvider.java; /cvs/debuggerjpda/ui/src/org/netbeans/modules/debugger/jpda/ui/BreakpointAnnotationProvider.java,v <-- BreakpointAnnotationProvider.java initial revision: 1.1 done
Radek, please verify this issue, thanks.
verified