The target applet or JVM process terminated unexpectedly

Question

I get the Target applet or JVM process exited abruptly sometimes and it doesn’t happen continuously, so I can’t track the log until the Java console closes. I tried to increase the heap size using

<PARAM name="java_arguments" value="-Xmx128m"> ,

<PARAM name="java_arguments" value="-Xmx300m"> ,

<PARAM name="java_arguments" value="-Xmx512m">

but does not work. The same question has already been asked. I also tried loading the Applet into a separate JVM using

<PARAM name="separate_jvm" value="true">

http://www.techques.com/question/1-11284843/uncaught-exception:-Target-applet-or-JVM-process-exited-abruptly---from-a-firefox-extension

uncaught exception: applet or JVM process suddenly quit due to firefox extension

https://stackoverflow.com/questions/17676722/target-jvm-seems-to-have-already-exited

Answer 1

If you can get your client to run the applet as fully trusted, you can do several things:

• Install the default exception handler and send it exception information.
• Call System.setOut () and System.setErr () and send the results to you.
• Set trailing locks and a security manager to find out when the JVM shuts down

Otherwise, you can try:

• Creating a non-daemon thread and sleeping forever to try to prevent the applet from closing by turning on at least one thread. (Having no experience with applets, I'm not sure if this will work).
• Use the Java logging system and give you information in the hope that the problem that causes the crash logs is before the crash.

Answer 2

Instead of launching the application directly from Windows, open a command-line editor session. When the program crashes, the window will not disappear, which allows you to read the "insides" at your leisure.