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 145130 - [65cat] Stop from "Finish Debgger Session" (Shift+F5) forcibly terminates the application
Summary: [65cat] Stop from "Finish Debgger Session" (Shift+F5) forcibly terminates the...
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 145947 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-26 12:45 UTC by _ theanuradha
Modified: 2008-09-17 13:46 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
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 _ theanuradha 2008-08-26 12:45:16 UTC 
[ JDK VERSION : 1.6.0_07 ]

Debug ANY Module Project and Stop from "Finish Debgger Session"
(Shift+F5) will lock down project (run lock on userdir not deleted
and give error that project is alrady running )

Workaround is manual delete lock file on userdir and it is really
painful when debugging projects
Comment 1 Martin Entlicher 2008-08-27 15:18:43 UTC 
Reproduced.
This is due to VirtualMachine.exit(0) call. This is certainly not polite.
Run -> Stop Build/Run works better, use this as a workaround.
Comment 2 Martin Entlicher 2008-09-02 16:33:55 UTC 
*** Issue 145947 has been marked as a duplicate of this issue. ***
Comment 3 Martin Entlicher 2008-09-11 15:34:22 UTC 
I do not have any problems with staled lock file in NetBeans (Build 080826). NetBeans starts despite the lock file exists.
Since there's workaround via Stop Build/Run, this is not a P2 defect.

Since it would be more polite to shut down the application in a way that it can do it's clean-up, moving to enhancement.
The current behavior can also be necessary if the debugged application is not responding or when it's not desired to
perform any additional work.
Comment 4 _ theanuradha 2008-09-11 17:59:58 UTC 
I SAY THIS IS BUG, if not way  "Finish Debgger Session is enable when debugging it should be disable than ?
Comment 5 _ theanuradha 2008-09-11 18:01:17 UTC 
As many developers we are using Shift+F5 to kill debug not mouse :-(
Comment 6 Martin Entlicher 2008-09-11 21:24:48 UTC 
What exactly do you mean by "THIS" when you say this is a bug?
The original problem you described was that you have to manually delete NetBeans' lock file in the userdir to be able to
start the next debugging session. I've find out that "THIS" is not necessary any more in recent 6.5 dev builds.

The current debugger behavior was there from the beginning. So I ask again, is there any severe problem with the
application being forcibly terminated without having a chance to do cleanup? Is there anything that justifies the P2
defect priority?

Also, please specify the NetBeans version you're using.
Comment 7 _ theanuradha 2008-09-12 14:44:59 UTC 
Ah I just now move to latest dev build and it seems  manually delete no need but if it is only if I want to run again 
but if I want to clean and build it wont allow me btw it is deferent story so we can drop to P3 or p4 feel free to do 
so
Comment 8 Peter Pis 2008-09-17 11:05:32 UTC 
Removing INCOMPLETE.
Comment 9 Martin Entlicher 2008-09-17 13:46:46 UTC 
O.K. thus moving back to enhancement, as a request to terminate the application in a way that allows it's cleanup.