457512 - firefox crashes

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[[e-mail]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

firefox browser crashes when i use it for long and with multi tabs

Reproducible: Always

Steps to Reproduce:
1.start firefox
2.use it for long hours
3.use Multi tabs in same site
Actual Results:  
it crashes 

Expected Results:  
continued

Comment 1

[Matthias Versen [:Matti]]

Please read http://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report

Comment 2

[fred]

Similar problem here.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

Reproducible: always (or so it seems).

Steps to reproduce:
1. start firefox
2. open multiple tabs in multiple windows
3. let firefox run overnight, while my session automatically locks;
4. next morning on unlocking my session, contemplate the nice Access Violation dialog box (last time: at address 0x600132EC writing to 0x33FEB00).
(Not sure how much of step 2 is necessary to reproduce the bug: do we need several windows ? several tabs ? tabs pointing to the same site ? I don't know yet.)

This seems related to a memory leak or at least excessive memory consumption. When the A.V. dialog was displayed (i.e. a few minutes ago, this morning in Western Europe), Task Manager gave the following numbers for Firefox:
- memory usage 64M
- virtual memory size 760M
- peak mem usage 471M
This is on a 2GB physical memory machine, that was barely using 3GB of memory (including Firefox) when the crash occurred.
Note that peak mem usage is significantly less than (current) virtual memory size, this does not look normal to me.
After hooking my debugger to Mozilla, an other application yielded an "out of memory" error. I suspect Mozilla's A.V. to be a byproduct of some ressource exhaustion. So not sure how much a stack trace would help. (Will try and provide one, next time; this time as usual, the automatic report tool failed to manifest itself on restarting firefox.)

That has happened with F 3.0.1 at least, probably 3.0.0; it did not happen with earlier version (2.X).

Comment 3

[fred]

Also, note that on restarting the same Firefox session, the memory consumption is much lower. In the previous case (760M of VM size at crash time), the restarted session was consuming about 130MB (both memory usage and VM size).

Comment 4

[Jo Hermans]

for the original reporter (Fred, you describe something else): no response in a long time, to enough data

see <https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report>