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 238030 - Awfully slow field breakpoint
Summary: Awfully slow field breakpoint
Status: RESOLVED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-06 09:49 UTC by zimi
Modified: 2014-02-14 16:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description zimi 2013-11-06 09:49:46 UTC 
I'm not sure is it a bug or it's simply has to be that way

I have some small/medium Java EE project.
I put some breakpoint on field somewhere in code and try to run application.

My application is now so slow that I'm not able to use it.
Netbeans is just all right.
No matter where I put breakpoint or where I'm in my application.

For example I may setup breakpoint in entity called Invoice and I'm not able to see login screen to my system because it's that slow.

Maybe this problem is related with my glassfish

I use Netbeans 7.4 and Glassfish 2.1
Comment 1 markiewb 2013-11-08 17:59:57 UTC 
Same for me. It helps a little to close the debugging view and to keep the call stack open. So there are less listeners which block the debugging UX
Comment 2 Martin Entlicher 2014-02-14 16:33:04 UTC 
It is true, that field breakpoints can cause significant slowdown of the application. For example I've tested field breakpoints in some AWT code and even if it's not hit (there is no communication between the debugger and the application), just the execution in the class that contains the field seems to cause a slowdown.

To be sure, you could try to debug with jdb.