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.
When the JPDA debugger stops on a breakpoint it calls (among other things) Line.show (Line.SHOW_GOTO) which in turn calls TopComponent.requestActive(). If I remove this last call I can speed up stepping in debugger two times. Please evaluate if code behind this call causes such slowdown. It eats ~100ms even if that component is already showing and active.
reassigning.
Created attachment 16055 [details] suggested patch.
can you please try to do your measurements agains with the provided patch? (Reassign back to me then) thanks.
This patch saves some 40-50 ms on average so this still unnecessarily takes 50-60 ms. Good progress though.
ok, I've applied the patch, along with another minor improvement (which however I don't believe to have major impact on the time) There's not much to do since the code in TopComponent.requestActive() -> WindowManagerImpl.topComponentRequestActive() -> Central.activateModeTopComponent() is pretty straightforward. The problem probably resides somewhere else than TopComponent.requestActive. closing as fixed.
I mark it closed because it's too old and I think, in current NetBeans 4.2 (Build 200507061800) the stepping in debugger is fast enough.
BTW you can use WindowManager.getDefault().getRegistry().getActivated() to get activated TC and if it is already equals to TC you want to activate you can omit call TC.requestActive(). It should be fastest way.