Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346612

Summary: better lock support needed after IDE crash
Product: [Eclipse Project] Platform Reporter: Richard J Moore <richardj_moore>
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: prakash, remy.suen
Version: 4.1   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:

Description Richard J Moore CLA 2011-05-20 05:41:21 EDT 
Build Identifier: BETA 0.5.0

If the IDE crashes, for example network connection dies when accessing the IDE remotely under VNC then workspace/.metadata/.lock is not deleted.  On restarting the IDE the popup appears inviting another workspace to be selected as it is assumed that the current is in use. After a crash, this is clearly not the case.

At the very least there should be help from the IDE to inform the user to delete .lock after a crash.

Even better would be for the IDE to give the user the option of overriding the lock when the popup is displayed.

And even better still is for the IDE to detect that is was not shutdown cleanly i.e to detect that no other instance of the IDE is running so it could only have no shut down cleanly.

Richard

Reproducible: Always

Steps to Reproduce:
1.start the IDE
2.kill the IDE  (eg log off)
3.start the IDE
Comment 1 Prakash Rangaraj CLA 2011-05-20 06:05:39 EDT 
(In reply to comment #0)
> Build Identifier: BETA 0.5.0

  What product are you using?
Comment 2 Prakash Rangaraj CLA 2011-06-03 02:05:15 EDT 
(In reply to comment #1)
> (In reply to comment #0)
> > Build Identifier: BETA 0.5.0
> 
>   What product are you using?

    Please reopen if you could reproduce it on Eclipse SDK
Comment 3 Richard J Moore CLA 2011-06-09 10:16:57 EDT 
The product I am using the the Linux on Power SDK.
Comment 4 Oleg Besedin CLA 2011-06-21 16:25:41 EDT 
I think lock behavior was changed around Eclipse 3.3. It should be rather hard to get into situation where a crash would prevent workspace lock from being released. At least that's what I see on Windows . 

I was not able to reproduce the error state on Windows 7.

*** This bug has been marked as a duplicate of bug 80734 ***