User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 This web site provides entry ways to several different atlantic satellite image loops. For example: http://www.ssd.noaa.gov/goes/east/tatl.html from which one can choose one of a group of still or looped images. The looped images call on Java, and provide the loops. Example: http://www.ssd.noaa.gov/goes/east/tatl/loop-vis.html The Fox crash occurs when I go to such a loop, then back up and choose another image area, such as: http://www.ssd.noaa.gov/goes/east/gmex.html with its own collection of looped images, such as http://www.ssd.noaa.gov/goes/east/gmex/loop-avn.html The error occurs when I go to a looped image, and then view different series of the image loops, either within the same image region, or in the different regions. Eventually, I get a crash, from a popup in Java, declaring that I have run out of space. Opening the Java Console and looking at the memory use, it has, indeed gone down 0% available. When this happens, Fox nearly freezes, allowing some migration between tabs, but little else. I can close the program, normally, agreeing to close all tabs. However, Fox remains in memory, and has to be closed manually using ctl-alt-del. The talkback mechanism, while active, does not produce a report. I have updated versions of Java 1.6 update 2, and Fox Reproducible: Sometimes Steps to Reproduce: 1. As above. 2. 3. I do not always get this crash, when viewing looped images, but my sense is that the more I look at, the more likely the crash [and memory consumption]. I would have no way of knowing if this is a failure of Fox, JAva or the NOAA/NHC website. Some element in that chain is not willing to let go of memory allocate for the purpose of providing the looped images, when going to subsequent loops.

Wanted to make sure that I clearly note that there are two ways to get to the looped images, one including using the multiple tabs feature, and one not. I would not be sure if one or the other way has a adverse impact on what might otherwise be a functional way to release memory inside Java, if such a command is issued Additionally, I note that I have adblock plus enabled, and tab mix plus.

This text file has a copy of the error reports provided by Java for this morning's crash, looking at satellite images. Text comes from the Java Detail Report for the initial popup, and the various dumps and data from the Java Console. I have also reported this bug to the website folks at NOAA/NHC, as I can't tell if its FOX or their doing [SSDWebmaster@noaa.gov and SABWebmaster@noaa.gov, per their contact URL on their webpages]

Modifying the bug to REPRODUCIBLE ALWAYS. I can watch the the Java Memory level drop down, with each view of each subsequent image loop, till it reaches a low percentage. One more image loop and then I receive the identical crash. EXPANDING THE BUG REPORT to report these additional FOX buggy behaviors 1. JAVA Crash as noted FREEZES Fox 2. Freeze does, however, allow program close using "X". However, the program does close gracefully, and leaves program in memory. 3. Talkback function does not trigger. I am guessing that closing a Tab or window, or backing up a Tab/Window DOES NOT CAUSE a release of committed JAVA memory.

at com.sun.deploy.ui.UIFactory.showErrorDialog(Unknown Source) at com.sun.deploy.ui.UIFactory.showExceptionDialog(Unknown Source) at com.sun.deploy.ui.UIFactory.showExceptionDialog(Unknown Source) Is there an error dialog you can close? this doesn't look like a gecko problem (it's vaguely amusing, but assuming you need to close this dialog and that it isn't closable, that'd be a bug in java.)

Ah. I need to explain better. There -is- a Java error dialog [out of memory] which i -can- close. Closing it, however, does nothing other than close the dialog box. Fox becomes disfunctional. I can not change tabs, the images in the NOAA/NHC series stop loading in mid sequence, and all I can do is "x" out of Fox, leaving the fox ghost in memory which i have to manually close.

do you still see problem if you use current beta, latest version of all plugins (for example flash v10 - check using about:plugins), java (1.6_0_13), etc started in safe mode https://support.mozilla.com/en-US/kb/Safe+Mode - latest beta http://www.mozilla.com/en-US/firefox/all-beta.html

As with different kinds of bugs in Fox, this one too has disappeared over the last 2 years. However, I haven't been, this year or during the '08 summer, doing quite as much looping of NOAA images, while hurricanes threatened. If many swoop in, I might again, in anticipation of work. I use the up-est to date Java, Fox etc, now, and have not, lately seen the Java problem. I suspect a Java and/or Fox fix, fixed the problem....

Well, closing as WFM for now. please reopen if it comes back.