Eclipse: Java was started but returned exit code -1073741571

Question

Eclipse is closing while loading any XML layout with this message Java was started but returned exit code -1073741571

my eclipse.ini

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120522-1813
-product
com.android.ide.eclipse.adt.package.product
--launcher.XXMaxPermSize
256M
-showsplash
com.android.ide.eclipse.adt.package.product
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms512m
-Xmx1024m
-Xss1024k
-Declipse.buildId=v21.0.0-519525

Solution 1

Thanks everyone for sharing solutions with me it seem that I had corrupted xml ( I am still not sure what corrupted means but it was forcing the IDE to crash) here is a snippet:

<com.android.example.EndlesScrollView...

    <FrameLayout...
        <LinearLayout...

Each time I tried to use Graphical layout view in eclipse the IDE crashes, All I did was to delete that XML totally and re-create it from scratch, it seems something wrong with the XML Tags which preventing the Graphical layout from correctly displaying the correct UI.

Solution 2

I noticed that the VM listed is: C:\Windows32\System\javaw.exe which I believe is the Java 7 installed version. My configuration is using one of the earlier installed JVMs (from my Eclipse.ini):

-vm
C:\Program Files\Java\jdk1.6.0_14\bin\..\jre\bin\client\jvm.dll

Maybe you should update Eclipse to use a 1.6 version of Java to run. From the Eclipse readme.html (found in the Eclipse install directory):

Specifying the Java virtual machine

Here is a typical Eclipse command line:

eclipse -vm c:\jdk1.4.2\jre\bin\javaw

Tip: It's generally a good idea to explicitly specify which Java VM to use when running Eclipse. This is achieved with the "-vm" command line argument as illustrated above. If you don't use "-vm", Eclipse will look on the O/S path. When you install other Java-based products, they may change your path and could result in a different Java VM being used when you next launch Eclipse.

Solution 3

Sometimes means that the workspace is corrupted.

Create a fresh workspace and try a XML file.

Comments

[Ahmad Kayyali]

thanks you very much for sharing this, I am testing this ASAP.

[Ahmad Kayyali]

I am testing this and let you know the results.