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 185579 - IDE locks up with 100% CPU when deleting Breakpoints
Summary: IDE locks up with 100% CPU when deleting Breakpoints
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Windows ME/2000
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on: 185810 190115
Blocks:
  Show dependency tree
 
Reported: 2010-05-06 05:23 UTC by bht
Modified: 2010-09-15 19:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Log files and thread dump in zip file (102.68 KB, application/octet-stream)
2010-05-06 05:23 UTC, bht
Details
Snapshot taken during deletion of breakpoints in current dev build (142.19 KB, application/octet-stream)
2010-05-09 16:05 UTC, Martin Entlicher
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bht 2010-05-06 05:23:15 UTC
Created attachment 98533 [details]
Log files and thread dump in zip file

IDE is in a debugging session in a Java EE Web project, but not suspended, still running normally.

As a response of the debug session star, the output window correclty highlights some invalid breakpoints.

I select all breakpoints and choose the context menu option delete for a cleanup.

CPU usage is at 100% for the next 10 minutes. At this stage I create a thread dump and terminate procss netbeans.exe.
Comment 1 Martin Entlicher 2010-05-09 16:05:45 UTC
Created attachment 98685 [details]
Snapshot taken during deletion of breakpoints in current dev build
Comment 2 Martin Entlicher 2010-05-09 16:07:41 UTC
I've reproduced this problem in current dev build. Deletion really seems to take longer than it has to.
Comment 3 Martin Entlicher 2010-05-09 20:59:50 UTC
Outline handles node icon and display name changes very inefficiently. It refreshes *whole* table because of a change of *one* icon. Due to that fact even scrolling is slow until all nodes are refreshed! This needs to be fixed in Outline.
Comment 4 Martin Entlicher 2010-05-10 16:40:20 UTC
Lowering the priority to P3, in current dev builds it does not take so long.

Because of the risky nature of issue #185810 this might not be further improved in 6.9.
Comment 5 Martin Entlicher 2010-05-18 11:52:13 UTC
We need to improve performance of Outline refresh in the next release.
Comment 6 Martin Entlicher 2010-09-15 19:50:43 UTC
It's fixed by the improvements in event handling - issue #185810.
http://hg.netbeans.org/main/rev/c97fab6053e1