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 205245 - slow display of list of breakpoints
Summary: slow display of list of breakpoints
Status: RESOLVED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.1
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2011-11-17 15:46 UTC by Marian Petras
Modified: 2013-01-08 21:38 UTC (History)
0 users

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 Marian Petras 2011-11-17 15:46:26 UTC 
It takes several seconds for the debugger to display a list of breakpoints, even if the list is very short (two breakpoints).

I have about 15 projects opened, all of them being Maven projects (four WAR projects, the rest are J2SE projects).

I have taken a screenshot of the callstack taken using the NetBeans self-profiling action but it got deleted soon due to bug #185688.
Comment 1 Marian Petras 2011-11-17 15:47:53 UTC 
From the callstack, it seemed that the debugger builds the (Maven) project every time the list of breakpoints is about to be displayed.
Comment 2 Marian Petras 2011-11-17 15:50:11 UTC 
System information:

NetBeans 7.1 Dev  (201110190600, i.e. post-beta), with updates
JDK 6u29  64-bit
Windows 7 Enterprise  64-bit
Intel quad-core CPU
Comment 3 Martin Entlicher 2011-11-21 16:59:10 UTC 
Debugger only checks if the breakpoints are in projects that are opened in NetBeans IDE. Debugger definitely does not initiate a build of the projects. Maybe that the build is triggered by the query? I'll try to reproduce...
Comment 4 Martin Entlicher 2012-05-31 15:08:36 UTC 
It's a pity that the call stack is not attached. We only call ProjectManager.getDefault().findProject(FileObject) to find the associated project and p.getLookup().lookup(SubprojectProvider.class) to find the sub-projects. If this triggers the build, it's bad.
Comment 5 Martin Entlicher 2013-01-08 21:38:36 UTC 
We'd need a profiler snapshot to see what's really happening there.
http://wiki.netbeans.org/FaqProfileMeNow