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 206227 - Shift+F5 often leaves lock in test userdir and restarting of debugging fails
Summary: Shift+F5 often leaves lock in test userdir and restarting of debugging fails
Status: RESOLVED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Ant (show other bugs)
Version: 7.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-10 22:37 UTC by mccorb
Modified: 2012-07-26 20:14 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 mccorb 2011-12-10 22:37:51 UTC 
Product Version = NetBeans IDE 7.1 RC2 (Build 201111302200)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0
Runtime = Java HotSpot(TM) 64-Bit Server VM 21.0-b17
Comment 1 Jiri Kovalsky 2011-12-12 08:24:48 UTC 
Updating summary. Original content:

Exiting debug session using shft-f5, frequently leaves lock file in testuserdir. When restarting a debug it fails because file exists. Output window used to show how to resolve. Now it does not. Newer users will get discouraged when debugging won't work.
Comment 2 Martin Entlicher 2012-01-02 16:43:28 UTC 
Unfortunately, the debugger finish does not call any shutdown hooks, it just halts the virtual machine. The test then does not know that it should do any cleanup.
The solution is to use the Stop button in the output window instead of shift-f5. There is no way to change this behavior from debugger.
Comment 3 tdanard 2012-01-18 17:03:58 UTC 
This change is a productivity killer. Please reconsider.
Comment 4 tdanard 2012-01-18 17:14:36 UTC 
I tested every "stop" button, none of them removes the lock file reliably . I tested the "Stop" button in the "output" window, the "Stop" button on the bottom right of the screen (Click to cancel process), the "Stop" button in the toolbar. 

The only way that works is to close normally the app being debugged.
Comment 5 tdanard 2012-07-26 20:14:27 UTC 
This issue seems to be gone in 7.2