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 254416 - Slower debugger in 8.1 beta
Summary: Slower debugger in 8.1 beta
Status: RESOLVED WORKSFORME
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.1
Hardware: PC Windows 8.1 x64
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2015-08-17 07:58 UTC by webhsw
Modified: 2015-08-31 06:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description webhsw 2015-08-17 07:58:22 UTC
The programs are running significant slower with debugger (Strg+F5) than in versions before 8.1
Example opening a complex JavaFX based window with database access (EclipseLink based) in Netbeans 8.1 = 20 sec, in Netbeans 8.0.2 = 3 sec and without debugger (F6) = 0.2 sec.
Comment 1 Jiri Kovalsky 2015-08-17 09:41:08 UTC
Martine, can you please evaluate this? Thanks!
Comment 2 Martin Entlicher 2015-08-17 13:15:50 UTC
It could be slow because of issue #241082, but that would be slow in 8.0.2 as well.

Can you please go to:
 Tools -> Options -> Java -> Java Debugger -> Visual Debugging
and un-check "Track locations of component hierarchy changes".
Does this improve the performance?

When you un-check also "Upload Visual Debugging agent to the target application", does that improve the performance even further?
Comment 3 webhsw 2015-08-18 05:50:46 UTC
In 8.0.2 both options are checked and it runs as described.
If I uncheck "Track locations of component hierarchy changes" in 8.1 the debugger runs as fast as in 8.0.2.
Checking or unchecking of "Upload Visual Debugging agent to the target application" does not change any performance.
Comment 4 Martin Entlicher 2015-08-27 14:29:43 UTC
After "Track locations of component hierarchy changes" is off by default (in issue #241082), both run and debug take sort of equal time for me.
I've tested on a Brick Breaker sample application. I do not think that the database access should do much with the debugging performance.

I'd be best if you could provide some sample application which we can use to reproduce the issue.

Do you have many breakpoints set? Breakpoints are being submitted when the appropriate classes load, which pauses the application execution for a while. If you have many breakpoints, their submission can slow the application execution down.
Comment 5 Martin Entlicher 2015-08-31 06:15:24 UTC
Resolving as works for me, I do not see much difference between Run and Debug. It may take some time only to submit breakpoints and that depends on their number.