Eclipse terminating, exit code 1

[Andrew Thompson]

Arrrgh! I was opening eclipse during a virus
scan (+ a ..few other things going on) and
it threw a spack, ..or in more technical terms
I got a dialog with the message;

JVM terminated. Exit code=1
C:\WINDOWS\system32\javaw.exe
-cp D:\eclipse\startup.jar org.eclipse.launcher.Main
-os win32
-ws win32
-arch x86
-showsplaxh D:\eclipse\eclipse.exe -showsplash 600

[ I suppose this is the fairy godmother of
advanced IDE's coming back at me for
reprimanding noobs who use them.. ;-) ]

http://www.ibm.com/search?q=+eclipse++JVM++terminated
did not reveal anything of use..

Can anybody advise how to fix this
problem, or where I'd look for more
information?

TIA

[ Damn them all, I'll return to the command
line if I have to ..so there! ]

 

[Tim Tyler]

Arrrgh! I was opening eclipse during a virus
scan (+ a ..few other things going on) and
it threw a spack, ..or in more technical terms
I got a dialog with the message;

JVM terminated. Exit code=1
C:\WINDOWS\system32\javaw.exe
-cp D:\eclipse\startup.jar org.eclipse.launcher.Main
-os win32
-ws win32
-arch x86
-showsplaxh D:\eclipse\eclipse.exe -showsplash 600

....and now it won't start again?

You know about deleting the ".lock" file - in your workspace?

 

[Tim Tyler]

The other thing to do is to kill any and all "eclipse" processes
before retrying.

 

[Andrew Thompson]

The other thing to do is to kill any and all "eclipse" processes
before retrying.

...
I shut-down and restarted the machine.
No good, still that same error. :-(

 

[Andrew Thompson]

....
You know about deleting the ".lock" file - in your workspace?

No I didn't, you mean this one?
'.metadata/.lock'

Should I delete the file, or the entire directory?

 

[Tim Tyler]

No I didn't, you mean this one?
'.metadata/.lock'
Yes.

Should I delete the file, or the entire directory?

The file is normally all that's needed.

If it's there, Eclipse won't start (though you should at least
get an error message) - and Eclipse *often* leaves it behind
when it crashes.

The whole thing is a pretty broken implementation, really...

 

[Andrew Thompson]

Unfortunately it has no effect. :-/

Eclipse still crashes with the same error
message and creates a new .lock file for
my amusement and edification.

I was considering uninstalling and reinstalling
Eclipse - that might kick the .lock out of it.

Any other ..less severe suggestions before I
try that?

[ BTW Tim - Your sig. seems rather ironic, in
this thread.. ;-) ]

 

[Sudsy]

Tim Tyler wrote:

If it's there, Eclipse won't start (though you should at least
get an error message) - and Eclipse *often* leaves it behind
when it crashes.

The whole thing is a pretty broken implementation, really...

Aha! So it's not just me who's found that Eclipse is a bit
"fragile". I keep my projects in separate directories just
so that WHEN (not IF) I have to reinstall Eclipse I don't
lose my work. I end up having to reload elements like the
JBoss-IDE and the apache jar (for certain tags) but I've
gotten used to it by now.
It also screws up royally under Linux if you accidentally
run two instances (a slip of the button finger) so I've
written shell scripts to prevent that from happening.
Finally, there are memory leaks such that you can only do
a limited number of build/redeploy cycles before you get
the OutOfMemoryError.
Still, when it DOES work it can enhance productivity if
you're developing EJBs.
Like everything else, it's a trade-off.

 

[Andrew Thompson]

Tim Tyler wrote:


Aha! So it's not just me who's found that Eclipse is a bit
"fragile".

Still, when it DOES work

You mean, Sudsy, you have spare time -
after what you've detailed above?

..it can enhance productivity if
you're developing EJBs.

..._anything_ else? ;-)

Like everything else, it's a trade-off.

My estimation of the benefit of that trade-off
is slipping more toward 'command line' by
the moment..

 

[Sudsy]

Andrew Thompson wrote:

You mean, Sudsy, you have spare time -
after what you've detailed above?

Okay, so it burned me on a few occasions and it DID waste
valuable time. It's still worth giving it a try, even if
only to determine the net gain/loss.

.._anything_ else? ;-)

It's also good for Struts, interestingly enough. I create
entire apps (JSPs, HTML pages, EJBs, servlets, custom tags,
ActionForms, Actions etc.) in Eclipse and the XDoclet tags
and ant support make for a nicely structured build
environment.

My estimation of the benefit of that trade-off
is slipping more toward 'command line' by
the moment..

I wouldn't throw in the towel just yet. If you stick with
it then you might develop an environment which works MOST
of the time.
I'll still keep my custom tools around, however.

 

[Tim Tyler]

[Eclipse]

Finally, there are memory leaks such that you can only do
a limited number of build/redeploy cycles before you get
the OutOfMemoryError.

Install more memory - and allocate more to Eclipse on the
command line when you start it.

 

[Sudsy]

[Eclipse]

Finally, there are memory leaks such that you can only do
a limited number of build/redeploy cycles before you get
the OutOfMemoryError.

Install more memory - and allocate more to Eclipse on the
command line when you start it.

So that I'll get more cycles before running into the same
problem? Delaying the inevitable? 2 GB not enough?
Sorry, but that's not a real solution, is it?

 

[Tim Tyler]

[Eclipse]

Finally, there are memory leaks such that you can only do
a limited number of build/redeploy cycles before you get
the OutOfMemoryError.

Install more memory - and allocate more to Eclipse on the
command line when you start it.

So that I'll get more cycles before running into the same problem?
Exactly.

2 GB not enough?

You are sure you have 2GB allocated to your Eclipse JVM?
Perhaps double-check with your documentation?

Sorry, but that's not a real solution, is it?

I never claimed I was offering something perfect.

Allocating more memory to Eclipse makes a substantial difference to
its usability here - since it spends less time almost out of memory,
less time crashing - and less time starting up.

 

[Sudsy]

Tim Tyler wrote:

Allocating more memory to Eclipse makes a substantial difference to
its usability here - since it spends less time almost out of memory,
less time crashing - and less time starting up.

Thank you for your confirmation. For a moment there I thought you
were trying to blame the instability on my particular hardware/
software configuration! ;-)
But it's still a nifty development platform when it's not busy
trying to toast itself.