Closed Bug 1082862 Opened 11 years ago Closed 7 years ago

Slow Firefox memory leak. (gigabyte used when left running in a VM for a week)

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
32 Branch
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: bugs, Unassigned)

Details

Was updating browser versions in one of my VMs. Launched FF32 beta, did check for updates, then was called away and left it alone for over a week while on vacation. When I came back, Windows was complaining about lack of memory. about:memory reported over 700 megs of heap unclassified that did not disappear in garbage collection. Firefox had the "about" window open (with the restart button for FF33 visible) and the about:home screen. The profile is basically unused apart from occasionally hitting kraken. I dumped process memory and about:memory details, and can attach to the bug if anyone is interested. The dump is over 200 megs compressed though.
Do you still see this issue when using a current version
Flags: needinfo?(bugs)
Whiteboard: [closeme 2018-01-15]
I have no idea if this can still be replicated. It takes a long time to do. It's simply a slow memory leak when FF is left up a long time. I'd have to setup a new VM env, leave it running, I really am not too interested in doing it right now sorry. I've had similar memory leaks over the years pretty consistently if FF is left open on Facebook or GMail - to the point of completely filling gigabytes of RAM on various linux machines. I don't know if those are reproducible post-quantum either... Maybe all the rearchitecture has cleaned a bunch of things up. I don't even know if I have the memory dump I saved all those years back, no one ever registered an interest in it. I guess there needs to be a close status. "Closed due to passage of years, no one cares, not even the original reporter"
Flags: needinfo?(bugs)
Hm... weird. Everything I wrote past the winking emoji vanished. Wonder if that's w3m or bugzilla's fault. Also all my whitespace vanished. Anyway, ended a bit moodily there. Wasn't intended. Feel free to close this out.
Thanks for the update. I guess the determining factor here is we don't have something that is actionable
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2018-01-15]
You need to log in before you can comment on or make changes to this bug.