From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010628 BuildID: 2001062815 If Mozilla is preloaded using -turbo switch, Java plug-in remains loaded after closing browser windows. Reproducible: Always Steps to Reproduce: 1. Launch mozilla -turbo 2. Launch mozilla 3. View any site containing Java 4. Close mozilla Actual Results: Java plug-in loads upon viewing first site with Java content. After closing all mozilla windows, Java plug-in remains loaded (Duke stays in the tray). Expected Results: Should unload Java plug-in when all mozilla windows are closed, to mimic behavior of non-turbo mozilla. Java plug-in does unload, of course, when the initial background mozilla process is manually terminated. I'm not sure if Java is actually unloadable without exiting mozilla altogether, but this quirk diminishes the appeal of -turbo mode.

confirming with win2k build 20010630..

Unfortunately, the Java plugin cannot be un-loaded from memory once loaded. Marking WONTFIX.

Given that loading the Java plug-in is a slow operation, and that defering loading it until it is first needed is basically a just-in-time lazy optimization of browser start-up speed, I don't see any problem with it staying loaded in -turbo mode. Indeed, one could even make a case that -turbo mode should preload the Java plug-in to avoid the hit of loading it when it is first needed.

SPAM: reassigning OJI bugs to new QA, pmac. (227 bugs)