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 141658 - Unusable debugger window, 100% CPU wasted
Summary: Unusable debugger window, 100% CPU wasted
Status: CLOSED DUPLICATE of bug 138496
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-25 09:38 UTC by Jaroslav Tulach
Modified: 2010-04-29 09:41 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 Jaroslav Tulach 2008-07-25 09:38:27 UTC 
Almost every debugging session ends with 100% being wasted, AWT blocked due to some kind of debugger window refresh. I 
am running on Mandriva Linux, KDE 3.5.x, Metal L&F.

"AWT-EventQueue-1" prio=10 tid=0x0808c400 nid=0x6f0e runnable [0xb2141000..0xb2141fb0]
   java.lang.Thread.State: RUNNABLE
        at java.awt.EventQueue.removeSourceEvents(EventQueue.java:898)
        - locked <0x708e9f20> (a org.netbeans.core.TimableEventQueue)
        at java.awt.Component.removeNotify(Component.java:6601)
        - locked <0x704457e0> (a java.awt.Component$AWTTreeLock)
        at java.awt.Container.removeNotify(Container.java:2625)
        - locked <0x704457e0> (a java.awt.Component$AWTTreeLock)
        at javax.swing.JComponent.removeNotify(JComponent.java:4699)
        at java.awt.Container.removeAll(Container.java:1231)
        - locked <0x704457e0> (a java.awt.Component$AWTTreeLock)
        at org.netbeans.modules.debugger.jpda.ui.debugging.DebuggingView$ViewRefresher.run(DebuggingView.java:638)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
        at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

The problem does not appear if I close the new debugging window as soon as I start the debugging session.
Comment 1 Daniel Prusa 2008-07-25 09:58:27 UTC 
Already reported in issue 138496 (P2).
It does not occur for each OS/CPU, but we take it as a serious problem. Fix is not trivial, it requires to implement a
suitable infrastructure allowing to refresh Debugging window optimally. I will try to do it till beta.
Comment 2 Daniel Prusa 2008-07-25 09:59:11 UTC 
Already reported in issue 138496 (P2).
It does not occur for each OS/CPU, but we take it as a serious problem. Fix is not trivial, it requires to implement a
suitable infrastructure allowing to refresh Debugging window optimally. I will try to do it till beta.
Comment 3 Daniel Prusa 2008-07-25 10:00:42 UTC 

*** This issue has been marked as a duplicate of 138496 ***
Comment 4 Quality Engineering 2010-04-29 09:41:49 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.