Closed
Bug 1248657
Opened 9 years ago
Closed 7 years ago
High heap-unclassified in network code on google sheets after long session
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 1249739
Performance Impact | none |
People
(Reporter: terrence, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets])
Attachments
(1 file)
688.45 KB,
application/x-gzip
|
Details |
Splitting this off from bug 1233481 comment 17. (In reply to Terrence Cole [:terrence] from comment #17) > Created attachment 8714366 [details] > bug1233481-dmd-report.txt.gz > > DMD is substantially slower, so I just left it to run all week and this > weekend. It has managed to accumulate 800MiB of reserved and 2GiB of mapped > memory in that time. Clicking on "minimize memory usage" does not affect > these sizes, so this is all either in use or leaked. I'll attach the memory > and DMD logs. > > A quick look at the DMD logs shows that most of the memory is over in net. > ~6,507 live ProxiedChannel2's; ~6,150 live nsHttpHeaderArrays; ~2,216 live > net::CacheEntry::HashingKeysWithStorage; ~2,111 live nSStandardURL's. Given > that this is all in one page, I'm going to guess this is a leak of some > sort. Although there's only 800MiB reserved, I'm guessing that fragmentation > in the C heap is absolutely murderous with all of these small allocations > sitting around for long periods. The difference I'm seeing in max commit > size might be down to --enable-jemalloc vs --disable-jemalloc for the DMD > build. > > Note: it was extremely windy this weekend in Santa Barbara, so the network > was up and down a ton. I'd be particularly suspicious of leaks in our error > paths here. I'm sure that :kar share the specific sheet with anyone with the cycles to investigate.
Updated•9 years ago
|
Whiteboard: [MemShrink]
Updated•9 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P1]
Updated•9 years ago
|
Whiteboard: [MemShrink:P1] → [MemShrink:P1][necko-backlog]
Comment 1•8 years ago
|
||
Is this a duplicate of bug 1249739?
Updated•8 years ago
|
platform-rel: --- → ?
Whiteboard: [MemShrink:P1][necko-backlog] → [MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleDocs][platform-rel-GoogleSheets]
Updated•8 years ago
|
Blocks: Meta-Hasal-GDoc
platform-rel: ? → -
Updated•8 years ago
|
Whiteboard: [MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleDocs][platform-rel-GoogleSheets] → [MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets]
Updated•8 years ago
|
Whiteboard: [MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets] → [qf-][MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets]
Comment 2•7 years ago
|
||
(In reply to Jan Steffens from comment #1) > Is this a duplicate of bug 1249739? Lets mark this as a duplicate.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-][MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets] → [MemShrink:P1][necko-backlog][platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets]
You need to log in
before you can comment on or make changes to this bug.
Description
•