Bug 15040 - Launcher doesn't detect VM crash
Summary: Launcher doesn't detect VM crash
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dejan Glozic CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-01 15:51 EDT by Peter Burka CLA
Modified: 2006-07-07 16:01 EDT (History)
0 users

See Also:

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 Peter Burka CLA 2002-05-01 15:51:37 EDT 
Build M5

If my runtime workbench session crashes, the debugger correctly detects that 
the processes are dead. However, if I try to launch a new runtime workbench, I 
get an error message telling me to close the running one first.

I thought that this might be because of the presence of a .lock file, but I 
can delete this file and the problem persists.

The only way to start a new session is to exit and restart Eclipse (the 
development workbench).

Note that I'm running a beta version of J9 for both sessions; this might be a 
contributing factor.
Comment 1 Peter Burka CLA 2002-05-01 16:31:14 EDT 
Interesting - if I delete the .lock file before I try to relaunch the first 
time, everything is Ok.

The problem only happens if I try to relaunch, get the error, and then delete 
the .lock file. Then I have to exit and restart.

May be related to Bug 15041
Comment 2 Dejan Glozic CLA 2002-05-01 17:33:24 EDT 
This problem was fixed post-M5 by removing the checks. PDE will not restrict 
launching in post-M5 builds.