Closed
Bug 792511
Opened 12 years ago
Closed 10 years ago
Shutdown leaks on TechCrunch
Categories
(Toolkit :: Storage, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mccr8, Assigned: mccr8)
References
Details
(Whiteboard: [MemShrink:P2])
Attachments
(1 file)
38.79 KB,
text/plain
|
Details |
1. Go to a TechCrunch page, like http://techcrunch.com/2012/09/19/take-public-transportation-heres-what-to-expect-from-the-maps-app-on-ios-6/ 2. Exit. Shutdown leak! I've noticed this for a while, I just haven't gotten around to filing it.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → continuation
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Updated•12 years ago
|
Component: Untriaged → Storage
Product: Firefox → Toolkit
Assignee | ||
Comment 3•12 years ago
|
||
I've been doing ref count logging, figuring out what is holding something alive, then repeating. I started with MemoryReporter_StorageSQLite. This is being held alive by moz::storage::Service. This, in turn, appears to be held alive by nsCookieService. I was unable to get refcount logging to work for that, but the only data structure that seems to hold a pointer to nsICookieService is nsHttpHandler, and there's one of those that is leaking so I assume that's the next link. That could just be a red herring, though. There is one leaking nsDocShell, maybe I should try examining that. That looks like the most "important" data structure in the bloat log.
Updated•12 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Assignee | ||
Comment 4•10 years ago
|
||
This doesn't seem to happen any more.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•