InformAction Forums

FF5, aurora -safe-mode.

Played back successfully. CPU usage seemed better controlled (in that it was more variable, where in Gecko 2.0 it was basically pegged at 25%).
Closing tab released CPU, though Mem Usage remained high, 1.43 GB.
Quitting & the firefox.exe process hung in memory released from memory (it just took a number of minutes).

FF6, (don't know what that's called, nightly) -safe-mode

Played back successfully. CPU usage seemed higher then FF5 or FF4 (possibly related to other apps running).
Closing tab took a while for CPU usage to subside. Mem Usage remained high, 1.56 GB. <-i'm giving it (lots of) time
[unknown of yet ] Quitting & the firefox.exe process hung in memory released from memory (it just took a number of minutes).

< work in progress ... >

@therube:
notice that for the memory being actually releasable you need to either close the current tab and open some additional tabs (10 or more), or close the current window, otherwise Firefox keeps the content viewer around just in case you want to reopen the tab at light speed.
Also, garbage collection is non-deterministic, so you may want to force it from about:memory in 6.0a1 (code name is just "Nightly" BTW).

I'm quoting my (work in progress, as I had edited up to before you replied).

FF6, (don't know what that's called, nightly) -safe-mode

Played back successfully. CPU usage seemed higher then FF5 or FF4 (possibly related to other apps running).
Closing tab took a while for CPU usage to subside. Mem Usage remained high, 1.56 GB. [10+ minutes later]. Did not release its memory. Would think it should have?
Quitting & the firefox.exe process released from memory (again it took a number of minutes).

Some questions you have answered, some I'll experiment more ...

nightly, so I'll capitalize the N, Nightly.

I did close the tab, though did not open more (& had no other Windows open) so I'll have to look at that part again.

therube wrote:FF6, (don't know what that's called, nightly) -safe-mode

Nightly, Aurora, Beta are the names for the non-stable states Firefox can be in, they are not code names for specific releases (comparable to Google Chrome's canary, dev and beta release channels):
http://www.mozilla.com/en-US/firefox/channel/

I give up (for now).

Crashed 4 times in succession (-safe-mode). Last try was with (most) everything else closed & still crashed.

Perhaps I need to reboot (memory fragmented?), but not in a position to.

Still with most everything closed down (including FF), switched to another User (Windows), & did some stuff.
Logged out of that user, came back to current user, fired up FF, only the one Window, & the clip played to the end.
Opened a dozen or so tabs (about:blank), & then finally alt+home (not, does not work in FF, so clicked the "house"), then closed the ro.me tab.

At that point, FF went not responding. I let it sit - a LONG time, never did get it back, eventually killed it.


Looks like there are existing bugs on ROME, https://bugzilla.mozilla.org/buglist.cg ... _id=267495.


To note: all my crashes & associated bug reports during this time have been (other then perhaps my comments) worthless, of the "...stackwalk.sh returned no header lines for reportid: 254551569; No thread was identified as the cause of the crash; No signature could be created..." ilk.

Win7 x86, 4GB ram, -safe-mode, or if with NoScript, v2.1.0.4rc10, SeaMonkey 2.1rc1, FF 4.0.1, FF 5 & 6 (20110514 builds).