Description of problem:
When you try to launch eclipse with a workspace which is in use, eclipse just
hangs at the splash screen stage.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start eclipse (or a runtime workbench)
2. Start eclipse again w/ the same workspace (or launch the runtime workbench again)
Eclipse hangs at the splash screen stage. Eventually the splash screen will go
away but the process is still running. If the first instance of eclipse is shut
down the hanging one will start up.
A "Workspace is currently in use" error should be shown.
This is probably because the osgi.locking property is being shut off.
Where is it being shut off? We used to do this in our launching script but not
Jeff, does this still happen? I think it might 'cause Anthony Green just
reported similar behaviour.
This is still happening as of 0.M5.12
When you can, please try with the M6 packages.
*** Bug 155755 has been marked as a duplicate of this bug. ***
This no longer happens when launching 2 run-time workbenches. It does however,
still happen when launching two separate eclipse instances with the same workspace.
forgot to mention verion: 3.1.0_fc-0.M6.12
Does this happen with upstream + proprietary JVM?
Andrew, upstream M6 + proprietary JVM reports the "workspace in use" error
I tracked this down to a libgcj/classpath bug. It's fixed upstream, but we'll
have to get the patch into our gcc RPMs.
This patch is in gcc* >= 4.0.0-4.
Closing RAWHIDE even though this hasn't been pushed yet.