User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 When loading applets that need a lot of time to start up (in our case a lot of database initialization), firefox simply kills the Java-Plugin after about ~20s. The whole out-of-process plugin is simply shut down (even a open java-console is closed), the area where the plugin should be is not painted. Happens with both Java6 u22 and u25 (new Plugin2), on Linux as well as on Windows-XP with FireFox4. Additionally, on Linux during applet loading the browser is completly un-responsive. Reproducible: Always Steps to Reproduce: 1. load the html page mentioned above (also attached) 2. wait 10-20s for firefox to kill the java process 3. Actual Results: firefox kills the plugin Expected Results: after the applet has finished loading/initialization, it should show up as expected.
Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 URL works for me on XP
Yes, we do this intentionally, although it is 45 seconds, not 20. You should perform long-running tasks from the event loop or a secondary thread, not during initialization.
On Linux with FireFox-4 its not more than 20s, my applet fails miserably.
just stop-watched, after 20s the applet is terminated. Well, does somebody have connections to Oracle. They should really adopt the plugin to not block the browser's event thread during initialization. However as ordinary user reporting bugs ... is almost useless.