Using separate_jvm to launch an applet in separate JVMs does not always work

Question

I have an applet that takes up enough memory, so we want to run it using a separate jvm = true so that each instance gets its own JVM (and not the shared one), so we don’t run out of memory on repeated calls. This works on our development boxes, but does not work on our customers' computers.

Are there any reasons for this?

This is a signed and reliable applet as we do 3D rendering.

Answer 1

, Sun Java 6 update 10 . , , JVM, 6u10. , , , JVM.

, , JVM , separate_jvm APPLET.

, JVM, . JVM JVM , JVM JVM.

Sun Java 6 u10 :

6u10 JVM:

• , JVM, , JVM.
• JVM ( , Java, java_arguments), JVM , , java_arguments.
• -Xmx : JVM , , java_arguments -Xmx256m, -Xmx128m, , , JVM. , -Xmx .

, java_arguments , JVM.

Answer 2

separate_jvm 1.6u10. JVM , .