JVM parameter 'Xmx' set in Java Control Panel ignored
Status: Beta
Brought to you by:
smichaud
For example, setting '-Xmx500M' in OS X Java Control Panel has no effect on an applet running in Firefox. It always uses the default 94Mb. I've tried setting JVM parameters for both 32 and 64-bit Java (but I believe Firefox uses 32-bit).
Java Embedding Plugin 0.9.7.3
MRJ Plugin 1.0-JEP-0.9.7.3
OS X 10.6.4
Firefox 3.6.7
If I remember right, the 96Mb limit is a hard limit imposed by the JVM
itself. What happens in Safari?
Safari using Plugin1 uses JVM parameters set in the Java Preferences utility. So if there is not parameters set, Safari will use 96Mb. If it set '-Xmx500M' for 64-bit Java in the Java Preferences utility, it will use 500Mb.
Chrome using Plugin2 (I think) behaves the same way.
Firefox using Plugin1 ignores the JVM settings. If I set '-Xmx500M' for both 32 and 64-bit Java in the Java Preferences utility, it will still use 96Mb. There should be a way for users to adjust these JVM parameters.
I've now finally had more time to look into this ... and I've
concluded that it's indeed a bug in the JEP.
I'll fix it in the next release.