Cory Daehn Reporter
	Description • 19 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

When Running Any version of Firefox since 1.0.1, The following issues have
cropped up:

1) Firefox will completely disappear when more than 1 java applet is running and
I receive an IM from one of these applets (most notably chatblazer and whatever
client manhunt.net uses) No trace whatsoever of the browser.  I could understand
crashing java or giving an error, but not the whole browser.
2) Once java applets start loading, the memory usage rapidly climbs in
firefox... on mine it went from 42Mb (Acceptable since I have 512Mb RAM) to
110Mb in RAM and 170Mb in swap. (Why does firefox allocate so much virtual
memory.  It's nuts and begins to really make the browser crawl after a while)
3) Firefox launches the Java VM Plugin with a 96M max heap space... this would
explain much of the memory usage.  There is no way to adjust this option.  it
ignores the setting in the Java control panel.  the -Xmx16M didn't work because
the 96M was already specified.

Reproducible: Always

Steps to Reproduce:
1. Launch Firefox 1.0.6 and start running pages with java applets
2.
3.

Actual Results:  
crash

Expected Results:  
work

java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version = 1.5.0_04-b05
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.5
java.vendor = Sun Microsystems Inc.
java.vendor.applet = true
java.vendor.url = http://java.sun.com/
java.vendor.url.applet = true
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
java.version = 1.5.0_04
java.version.applet = true
java.vm.info = mixed mode, sharing
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.5.0_04-b05
javaplugin.maxHeapSize = 96m
javaplugin.nodotversion = 150_04
javaplugin.proxy.config.list = 
javaplugin.proxy.config.type = browser
javaplugin.version = 1.5.0_04
javaplugin.vm.options = -Djava.class.path=C:\PROGRA~1\Java\JRE15~2.0_0\classes
-Xbootclasspath/a:C:\PROGRA~1\Java\JRE15~2.0_0\lib\deploy.jar;C:\PROGRA~1\Java\JRE15~2.0_0\lib\plugin.jar
-Xmx96m -Djavaplugin.maxHeapSize=96m -Xverify:remote
-Djavaplugin.version=1.5.0_04 -Djavaplugin.nodotversion=150_04
-Dbrowser=sun.plugin -DtrustProxy=true
-Dapplication.home=C:\PROGRA~1\Java\JRE15~2.0_0 -Xmx16M
-Djava.protocol.handler.pkgs=sun.plugin.net.protocol

	Adam Guthrie
	Comment 1 • 19 years ago

Please provide a talkback ID for the crash. http://kb.mozillazine.org/Talkback

	Dieter Menne
	Comment 2 • 18 years ago

This bug is probably similar to the one reported here. Try 
 
http://www.menne-biomed.de/swallow/jswallow3d.php

This application uses javaview and a custom java application available as sources in 
http://www.menne-biomed.de/swallow/jswallow3d.txt.
Konrad Polthier, the author of javaview, has recommended to explicitely destroy memory, so a message is printed out on the console when the destructor is called.

On each selected swallow, memory decreases. Manual garbage collection does not help. After 4-5 swallows loaded, system crashes, firefox hangs in memory and must be removed from memory via task manager.

Sorry to say: this works perfectly under IE, and it worked under earlier versions of firefox (don't know exactly at what version is stopped working).

Dieter Menne

	Dieter Menne
	Comment 3 • 16 years ago

This bug still exists two year after being reported. In addition to IE, I tested the application under Safari and it works perfectly there.

Is there anything I can do to get someone to look after this seriously?

Dieter Menne

	timeless
	Comment 4 • 16 years ago

you reported more than one "problem". this is against the bug reporting guidelines. => INVALID.

none of your problems are particularly useful or clear and likely to be resolved.

plug-in bugs should probably be reported to your plug-in vendor (sun) via their bug tracker.

if you want to complain about crashes,
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg

will enable you to get a stack trace so that you could actually report crashes to someone.

if you want to complain about how the plug-in behaves including its initial values, you should use java bug parade.