Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Zombie Eclipse 3.5 Processes on Windows(Multiple Eclipse 3.5 processes using the same workspace)
Zombie Eclipse 3.5 Processes on Windows [message #524387] Wed, 31 March 2010 18:29 Go to next message
Bob Bick is currently offline Bob BickFriend
Messages: 11
Registered: July 2009
Junior Member
My company has experienced several occurrences in which two Eclipse 3.5 processes (and javaw.exe) are using the same workspace on Windows XP.

They think that only one Eclipse instance is running since only one shows in the process tray. However, when we run process explorer (procexp.exe) on their machine, we can see another Eclipse.exe (and javaw.exe) that is using the same Eclipse workspace.

This situation causes strange building behavior (e.g. building goes on forever).

To resolve the problem, I kill the zombie Eclipse 3.5 process and then Eclipse behaves well again. But, this is a big hassle because it is hard to get developers to detect this problem in the first place.

Has anyone else ever experienced this issue? Any ideas on how to keep it from occurring?

Thanks in advance,
B
Re: Zombie Eclipse 3.5 Processes on Windows [message #524412 is a reply to message #524387] Wed, 31 March 2010 20:08 Go to previous message
Bruce Kelly is currently offline Bruce KellyFriend
Messages: 63
Registered: July 2009
Member
"Bob Bick" <bbick@netjets.com> wrote in message
news:hp049p$6n4$1@build.eclipse.org...
> My company has experienced several occurrences in which two Eclipse 3.5
> processes (and javaw.exe) are using the same workspace on Windows XP.
> They think that only one Eclipse instance is running since only one shows
> in the process tray. However, when we run process explorer (procexp.exe)
> on their machine, we can see another Eclipse.exe (and javaw.exe) that is
> using the same Eclipse workspace.
>
> This situation causes strange building behavior (e.g. building goes on
> forever).
>
> To resolve the problem, I kill the zombie Eclipse 3.5 process and then
> Eclipse behaves well again. But, this is a big hassle because it is hard
> to get developers to detect this problem in the first place.
>
> Has anyone else ever experienced this issue? Any ideas on how to keep it
> from occurring?
>
> Thanks in advance,
> B

I have seen this happen when Eclipse is used to launch a java application
(A) that then launches another application (B) and then A exits with B still
running.

If you shutdown Eclipse it appears to close, but the processes are still
there until application B terminates.

If the launch configuration used to lauch application A is changed to *not*
allocate a console, then the problem doesn't happen.

I have also had the Eclipse UI lockup when trying to launch A again with B
still running. This problem doesn't happen if no console is allocated for A.
The lockup ends when application B terminates.

Namaste, Bruce
Previous Topic:Command Binding Scheme
Next Topic:Integrated php and perl debugging, is that possible with Eclipse
Goto Forum:
  


Current Time: Sat May 25 23:51:42 GMT 2024

Powered by FUDForum. Page generated in 0.03393 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top