Closed
Bug 1015602
Opened 12 years ago
Closed 11 years ago
division by zero crash or bin-unused and heap-chunks too huge (jemalloc3)
Categories
(Core :: Memory Allocator, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| b2g-v1.3T | --- | fixed |
People
(Reporter: jbeich, Assigned: jbeich)
References
Details
Attachments
(1 file)
|
1.36 KB,
patch
|
erahm
:
review+
|
Details | Diff | Splinter Review |
Bug 1006769 Part 1 added memory reporters for |chunksize| and |bin_unused| (new) fields of jemalloc_stats_t. Calculating the former is trivial but the latter may need upstream help or poking with dalloc bins stats.
Explicit Allocations
32,885.73 MB (100.0%) -- explicit
├──32,803.28 MB (99.75%) -- heap-overhead
│ ├──32,801.46 MB (99.74%) ── bin-unused
│ └───────1.82 MB (00.01%) ++ (3 tiny)
└──────82.45 MB (00.25%) ++ (22 tiny)
Other Measurements
57.72 MB ── heap-allocated
3,366,480 ── heap-chunks
0.00 MB ── heap-chunksize
59.54 MB ── heap-committed
61.00 MB ── heap-mapped
3.15% ── heap-overhead-ratio
Comment 1•11 years ago
|
||
Comment on attachment 8428252 [details] [diff] [review]
workaround
Review of attachment 8428252 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm!
Attachment #8428252 -
Flags: review+
I've wanted to update the comment but there's probably not much point. Except for file/function_name it already carries enough information. Adding a wrong hint is worse.
// We could get this value out of base.c::base_pages, but that really should
// be an upstream change, so don't worry about it for now.
Keywords: checkin-needed
Comment 3•11 years ago
|
||
Assignee: nobody → jbeich
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Comment 5•11 years ago
|
||
Do we need land it on v1.3t? It blocks bug 1006769.
status-b2g-v1.3T:
--- → ?
Updated•11 years ago
|
Flags: needinfo?(fabrice)
Comment 6•11 years ago
|
||
Flags: needinfo?(fabrice)
Updated•11 years ago
|
blocking-b2g: --- → 1.3T?
You need to log in
before you can comment on or make changes to this bug.
Description
•