Bug 180212 - [launcher] -XX:MaxPermSize argument causes new launcher to fail
Summary: [launcher] -XX:MaxPermSize argument causes new launcher to fail
Status: RESOLVED DUPLICATE of bug 188968
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-30 10:57 EDT by Ben Pryor CLA
Modified: 2007-11-01 13:34 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Pryor CLA 2007-03-30 10:57:18 EDT 
Build ID: I20070323-1616

Steps To Reproduce:
This is with Eclipse 3.3M6, Sun Java 1.6, and WinXP. 

When launching Eclipse (using launcher JNI invocation mode) and passing the MaxPermSize vm argument, the process immediately terminates with the JVM termination dialog.

When specifying the full path to javaw.exe (non JNI invocation mode) it works fine.

Working:
eclipse.exe -vmargs -Xmx1024M
eclipse.exe -vm "c:\Program Files\Java\jdk1.6.0\bin\javaw.exe" -Xmx1024M -XX:MaxPermSize=256M

Not working:
eclipse.exe -vmargs -Xmx1024M -XX:MaxPermSize=256M


More information:
Comment 1 Ben Pryor CLA 2007-03-30 11:07:36 EDT 
Correction: the old style of launching is working using the following command line (I left off the -vmargs above):
eclipse.exe -vm "c:\Program Files\Java\jdk1.6.0\bin\javaw.exe" -vmargs -Xmx1024M
-XX:MaxPermSize=256M
Comment 2 Oleg Besedin CLA 2007-03-30 11:13:55 EDT 
Most likely when you do not specify a VM, some other, non-Sun VM gets picked up by the launcher. 

As any "other" VMs don't konw about -XX arguments, the default behaviour of those VMs would be to close immediately. 

Can you check which VM is actually used to run Eclipse if you don't specify "-vm" option?
Comment 3 Ben Pryor CLA 2007-03-30 11:36:22 EDT 
When not explicitly specifying a VM, the launcher is using a Sun JRE 1.6 (c:\Program Files\Java\jre1.6.0). I can verify this from inside Eclipse using the configuration details dialog and from outside using process explorer to see what DLLs are loaded for the eclipse.exe process.

When explicitly specifying this same VM and using the old style of launching (specifying the full path to javaw.exe) everything works fine, and the MaxPermSize argument is accepted.

This invocation fails:
eclipse -vm "c:\Program Files\Java\jre1.6.0\bin" -vmargs -Xmx1024M -XX:MaxPermSize=256M

This invocation works:
eclipse -vm "c:\Program Files\Java\jre1.6.0\bin\javaw.exe" -vmargs -Xmx1024M -XX:MaxPermSize=256M
Comment 4 Andrew Niefer CLA 2007-11-01 13:34:09 EDT 

*** This bug has been marked as a duplicate of bug 188968 ***