Eclipse IDE gets terminated(closed) sometimes in my Windows Vista?

Hi, sometimes my eclipse IDE gets terminated or closed all of sudden with an error msg "JVM Terminated. exit code =1" (see attachment for more info).
can somebody tell me whats wrong with it?
iam using 64bit os on Intel core 2 duo processor with 4gb ram.

thanks

Check the log file.

Mostly I chalk things like this up to "Vista is a really horrible OS."

You could also try the 32-bit version; I always had fewer problems with that.

i checked log file then what?
come on please tell me the solution as it is an uncommon error which can be rarely found on the internet.

Vinod Vijay wrote:i checked log file then what?

Tell us what's in it.

Did you see the rest of my post? If this is a ran dom, non-deterministic crash it'll be nearly impossible for us to help.

If Eclipse is just crashing and you're really not told anything about what is wrong, you might want to increase the amount of memory allocated to the JVM in which Eclipse is running. Have a look at your eclipse.ini file (in the Eclipse installation directory) and see the -Xms and -Xmx options. The -Xms specified the minimum heap (memory) size, while the -Xmx spcifies the maximum heap size.

Perhaps you could bump up the maximum (although if your eclipse.ini has the maximum set to 512m as mine does, I can't imagine this is not already large enough).

Do you know which version of JVM you are using? Based on the error pop-up I would say that you are using a 32-bit version of the last JRE that was installed. You should make sure that you are using the very latest JVM, I recall when Vista came out that the JVM version available at that time had all kinds of issues with Vista.

One thing you could do is download and install the latest 32-bit JDK from the Sun web site and then edit the eclipse/eclipse.ini file to use that JDK. You can do that by adding these lines (change the JVM path for your system):

-vm
c:/apps/java/jdk1.6.0_18/jre/lib/client/jvm.dll

Peter Johnson wrote:-vm
c:/apps/java/jdk1.6.0_18/jre/lib/client/jvm.dll

That path (jre/lib/client) doesn't exist on my installed JDK (1.6.0_06). I have jre/bin/client though. Did this change between 1.5 and 1.6?

Also, I found it was important where these lines were placed within the eclipse.ini file. If I placed them at the beginning or at the end, they were not recognized. I had to place them near the top.

Is there a rule, like they must appear after this arg, but before that arg?

Thanks (hoping my hijack will help the OP),

Mark E Hansen wrote:Perhaps you could bump up the maximum (although if your eclipse.ini has the maximum set to 512m as mine does, I can't imagine this is not already large enough).

I can't run Eclipse with anything less than a 1G max; I can't even imagine running it in 512M--my drives would thrash.

Mark wrote:That path (jre/lib/client) doesn't exist on my installed JDK (1.6.0_06). I have jre/bin/client though. Did this change between 1.5 and 1.6?

The 'lib' is a typo, it should be 'bin'. Sorry.

Mark wrote:Is there a rule, like they must appear after this arg, but before that arg?

I usually put the -vm entry right before the -vmargs entry. I think that anywhere before -vmargs should work.

David wrote:my drives would thrash.

Your disk drives thrash if you are using a smaller heap size (-Xmx)?

Peter Johnson wrote:

Mark wrote:Is there a rule, like they must appear after this arg, but before that arg?

I usually put the -vm entry right before the -vmargs entry. I think that anywhere before -vmargs should work.

Yes, that seems to work. However, you must place it after the -startup ... Jar args.

Thanks for the clarification.

Peter Johnson wrote:

David wrote:my drives would thrash.

Your disk drives thrash if you are using a smaller heap size (-Xmx)?

Yeah, 512M isn't enough for a responsive Eclipse, IMO.