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 184797 - Cannot Continue, Step Over etc.
Summary: Cannot Continue, Step Over etc.
Status: VERIFIED DUPLICATE of bug 182064
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-23 05:52 UTC by Tomas Mysik
Modified: 2010-05-11 14:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screenshot (209.41 KB, image/png)
2010-04-23 05:52 UTC, Tomas Mysik 		Details
profiler snapshot (58.51 KB, application/octet-stream)
2010-04-23 06:15 UTC, Tomas Mysik 		Details
Similar problem different NPS (too much repaint in editor + MyProperty.getValue blocked in AWT) (81.66 KB, application/x-netbeans-profiler)
2010-04-29 13:06 UTC, Jaroslav Tulach 		Details
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 Tomas Mysik 2010-04-23 05:52:40 UTC 
Created attachment 97894 [details]
screenshot

It happens to me often that I cannot Continue, Step Over etc., have a look at the screenshot. Unfortunately, the steps to reproduce seem to me to be just:
- start debugging and it simply will happen

Product Version: NetBeans IDE Dev (Build 100422-793fcb5a7f81)
Java: 1.6.0_16; Java HotSpot(TM) 64-Bit Server VM 14.2-b01
System: Linux version 2.6.31-20-generic running on amd64; UTF-8; cs_CZ (nb)
Comment 1 Tomas Mysik 2010-04-23 06:07:32 UTC 
Update: If one waits for a long time, buttons are active again but they cannot be nearly used because the IDE is very busy and clicking on any "debug" button seems to do nothing...
Comment 2 Tomas Mysik 2010-04-23 06:14:57 UTC 
I must change the priority to P2 because I can't debug any more even if I restarted the debugged application (another NB instance) and attached the NB debugger again (the current debugged line is not highlited, IDE is busy). I will attach a snapshot.

Please evauluate, thanks.
Comment 3 Tomas Mysik 2010-04-23 06:15:44 UTC 
Created attachment 97895 [details]
profiler snapshot
Comment 4 Tomas Pavek 2010-04-27 13:17:37 UTC 
Looks similar to bug 182064. The snapshot does not look like there would be much happening in debugger. What is the CPU when the debugger gets to this state, is it high? Is it consumed by the debugging IDE?

What I can see in the snapshot:
* There are some 'DebuggingView Refresh Scheduler' threads, but not doing much (just a few ms).
* Then there is 'JDI Target VM Interface', but it's not clear what this thread is really doing, spending all time in native socket read.
* And there is a long wait in 'Debugger operator thread' on com.sun.tools.jdi.EventQueueImpl.removeUnfiltered() - which I don't know if it matters or not.

Anyway, if you can reproduce it, we should probably stop by and see it live...
Comment 5 Tomas Mysik 2010-04-27 17:36:09 UTC 
(In reply to comment #4)
> What is the CPU when the debugger gets to this
> state, is it high? Is it consumed by the debugging IDE?

Yes, it was high and seemed to me related to the IDE.

> Anyway, if you can reproduce it, we should probably stop by and see it live...

That would be perfect - I know what I was doing, we can try to reproduce.
Comment 6 Jaroslav Tulach 2010-04-29 13:06:17 UTC 
Created attachment 98278 [details]
Similar problem different NPS (too much repaint in editor + MyProperty.getValue blocked in AWT)
Comment 7 Tomas Pavek 2010-05-04 09:38:25 UTC 

*** This bug has been marked as a duplicate of bug 182064 ***
Comment 8 Marian Mirilovic 2010-05-11 14:26:36 UTC 
verified duplicate