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 188354 - Debugger keeps running after stopping
Summary: Debugger keeps running after stopping
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2010-07-04 07:46 UTC by Tomas Mysik
Modified: 2010-08-01 09:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
profiler snapshot (24.26 KB, application/octet-stream)
2010-07-04 07:46 UTC, Tomas Mysik 		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-07-04 07:46:47 UTC 
Created attachment 100591 [details]
profiler snapshot

It happens from time to time that debugger keeps running even if one detaches it. Have a look at the attached profiler snapshot.

P2 because one needs to restart the IDE.

Product Version: NetBeans IDE Dev (Build 100702-a44c03e9ad9b)
Java: 1.6.0_20; Java HotSpot(TM) 64-Bit Server VM 16.3-b01
System: Linux version 2.6.32-23-generic running on amd64; UTF-8; cs_CZ (nb)
Comment 1 Martin Entlicher 2010-07-28 14:40:08 UTC 
Tomas, can you please provide some steps how can we reproduce it?
The profiler snapshot does not indicate that debugger is running. There are no threads that process debugger events. If debugger actions are still active in the toolbar, then there is some problem in the cleanup after debugging finishes.

In the snapshot I see only building of breakpoint groups. It's possible that this process somehow blocks closing of debugger. This was improved in bug #188314.

So, hopefully this was also fixed by this change, can you please verify?
Comment 2 Tomas Mysik 2010-08-01 09:55:28 UTC 
(In reply to comment #1)
> So, hopefully this was also fixed by this change, can you please verify?

I will try and reopen if the problem still exists. Thanks.