Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363575

Summary: Eclipse Unable to start with JVM heap Size -Xmx1024m
Product: [Eclipse Project] Equinox Reporter: Nattu <natarajan.thirumeni>
Component: LauncherAssignee: Project Inbox <equinox.launcher-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: flemingb, satyam.kandula
Version: 3.6.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Nattu CLA 2011-11-11 07:03:17 EST
Build Identifier: Build id: M20110210-1200 (Eclipse SDK)

Eclipse 3.6.2 on Win XP3

Here is the copy of the eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222
-showsplash
org.eclipse.platform
--launcher.defaultAction
openFile
-vmargs
-Xms100m
-Xmx1024m

If use -Xmx348m then it works fine. It also works fine when removing -showsplash
org.eclipse.platform

When we try to eclipse vai command line: eclipsec.exe

Library JVMJ9VM015W j9gc24 (2) Initialization Error: Failed to instantiate heap. 1024M was requested

It is worth to mention my OS Win XP SP3 ENGLISH, I changed the locale to use Japanese. 

Reproducible: Always

Steps to Reproduce:
1. Reproducible in my environment. Configure eclipse.ini file to use -Xmx1024m and -showsplash
org.eclipse.platform
2. Start Eclipse
3. You will unable to start the Java Virtual Machine
Comment 1 Eclipse Genie CLA 2019-10-12 11:54:57 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.