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.

Bug 200206

Summary:	F8 and cntrl-F7 much slower in debugger than F5
Product:	debugger	Reporter:	mccorb
Component:	Java	Assignee:	Martin Entlicher <mentlicher>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	6.x
Hardware:	PC
OS:	Windows Vista
Issue Type:	ENHANCEMENT	Exception Reporter:

Description mccorb 2011-07-18 12:41:09 UTC

Suppose I have a method and I don't want to step into it. If I set a breakpoint at the line following the method and then press F5, the method takes a reasonable amount of time to execute. However, if I press the F8 key (a mistake I always regret when the method does a lot of stuff like iterating over large datasets etc.) the debugger ends up doing huge amounts of work and taking orders of magnitude more time. The same once I trace into a method and then decide I want to step back out using ctrl-F7. When I bring up the windows task manager and look at the cpu%, the netbeans debugger, not the app I am debugging is consuming the cpu.

Either F8 or ctrl-F7 should be redone to act as though a breakpoint was set on the line following the method I either chose to step over or trace into.

Although this may seem like a small problem, it is a pretty big deal from the standpoint of debugging efficiency. Also it seems as though it would be fairly straighforward to modify, giving a pretty big payoff for maybe not much work.

thanks

Comment 1 Martin Entlicher 2011-07-18 15:51:36 UTC

Thanks for letting us know. We have improved some performance into NB 7.0, but it may not help in this case. I'll check it if I'll be able to reproduce.

Comment 2 dellasavia 2016-07-22 21:27:57 UTC

It was happens whit me too. My NB is 7.4 (Ubuntu 64bits)

Comment 3 peathal 2017-02-28 10:28:11 UTC

Is there any news on this?