What s going on with eclipse auto close

Eclipse is automatically closed when it is opened.

The best solution:

Delete the file under the workspace directory. metadata/.plugins will do the trick.

Here's how: If you find the eclipse directory, you can see the following:

startup

plugins/

plugins/

product

openfile

256mshowsplash

openfile

vmargs

xms40m

xmx512m

Modify it to the following to start EclipseStartup

plugins/

plugins/

product

openfile

128mshowsplash

openfile

vmargs

xms40m

xmx256m

What is the message of what prompts for automatic shutdown?

You try to double the size of the will not hang up.

Here's how: If you find the eclipse directory, you can see the following:

startup

plugins/

plugins/

product

openfile

256mshowsplash

256mopenfile

vmargs

xms40m

xmx512m

Modify it to the following to start EclipseStartup

plugins/

plugins/

product

openfile

128mshowsplash

128mopenfile

vmargs

xms40m

xmx256m

I haven't set it up, and I use it directly after unzipping it.

There has never been a problem of freezes and crashes.

Most of this is due to insufficient storage.

It should be a problem with the file, you follow this configuration.

Here's how: If you find the eclipse directory, you can see the following:

startup

plugins/

plugins/

product

openfile

256mshowsplash

256mopenfile

vmargs

xms40m

xmx512m

Modify it to the following to start EclipseStartup

plugins/

plugins/

product

openfile

128mshowsplash

128mopenfile

vmargs

Delete the file under the workspace directory. metadata/.plugins will do the trick.

Two workarounds: 1. Reinstall the JDK to a directory without spaces and Chinese characters. 2. Modify Add 2 lines in front of -vmargs:

vm "$ your jdk bin"Note that it's two lines, and that double quote is required for a directory or file name with a space.

android-support-v4, due to different versions, the class is incomplete, causing eclipse to close automatically. With standard v4 under the SDK, the auto-shutdown issue was resolved.

The first time the auto-shutdown occurred, it was changed that the import method of v4 was changed, and the issue of v4 under the reference SDK was resolved. However, at that time, the import method of v7 was also changed, and it is not clear what caused the automatic shutdown.

A few days ago, due to the import of a third-party project, it was automatically shut down, and it was almost impossible. Due to tracking the inheritance relationship, it is found that there is no connection in the inheritance, and I suspect that there is a problem with v4, and I check v4 and find that there are many classes missing; It was thought that this was the cause of the automatic shutdown, and the problem was solved after the replacement.

Is it a flashback?

If so, you can follow these steps::

1.Open the workspace directory for Eclipse2Delete it. metadata directory.

The best solution:

Delete the file under the workspace directory. metadata/.plugins will do the trick.

Memory problems are recommended for landlord settings. The following is the recommended configuration for 1 GB of memory-vmargs-xms128m-xmx512m-xx:permsize=64m-xx:maxpermsize=

It may be a problem with the plugin, you try auto-update.

Just change your workspace!

Here's how: If you find the eclipse directory, you can see the following:

startup

plugins/

plugins/

product

openfile

256mshowsplash

256mopenfile

vmargs

xms40m

xmx512m

Modify it to the following to start EclipseStartup

plugins/

plugins/

product

openfile

128mshowsplash

128mopenfile

vmargs

xms40m

xmx256m

It should be a problem with the file, you follow this configuration.

Here's how: If you find the eclipse directory, you can see the following:

startup

plugins/

plugins/

product

openfile

256mshowsplash

openfile

vmargs

xms40m

xmx512m

Modify it to the following to start EclipseStartup

plugins/

plugins/

product

openfile

128mshowsplash

openfile

vmargs

This problem is that the software itself is relatively large, due to the version or computer configuration, the software often dies, and there is basically no way to solve it, only through the installation of a more stable version, and the installation of some plug-ins.