JDK-6283276 : multiple -Xms Java plugin params kills browser
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.2
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2005-06-09
  • Updated: 2010-04-02
  • Resolved: 2005-06-24
Related Reports
Relates :  
Description
FULL PRODUCT VERSION :


ADDITIONAL OS VERSION INFORMATION :
Windows XP

EXTRA RELEVANT SYSTEM CONFIGURATION :
java version 1.4.2_06

A DESCRIPTION OF THE PROBLEM :
I made a typo entering the java runtime params in the control panel.  What I wanted was
-Xms4m  -Xmx256m

what I actually typed was
-Xms4m  -Xms256m

visit a page that uses java and the browser dissapears!  No idea if it errored or what - behavior was exactly the same as when I click on the "x" button on the top right of the browser window

  Fix the params & everything works fine

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
add the following to the java plugin runtime parameters
-Xms4m  -Xms256m

view a web page that uses java and the browser exits
[browser being IE, firefox & mozilla)

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expected at least an error message or a popup
What I didn't expect was the browser disappearing!

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
fix the typo
###@###.### 2005-06-09 16:39:02 GMT

Comments
EVALUATION This is user's error. Will not fix. As a note, browser behavior might be different from one version of JRE to another. I tried to reproduce the problem with JRE 6.0 with mozilla browser on solaris. The browser did not crash. I got error messages in the terminal window from where I started the browser that VM could not start properly: Gtk-WARNING **: invalid cast from `GtkSuperWin' to `GtkWidget' Invalid initial heap size: -Xms4m Xms356m Could not startup JVM properly! java_vm process: could not start Java VM Could not read ack from child process Plugin: Java VM process has died. plugin: java process exited with status 3 Could not start JavaVM! Above is a pretty good explanation on what went wrong with VM. It is also similar to behavior of java command itself. ###@###.### 2005-06-24 00:00:24 GMT
24-06-2005