Closed
Bug 678126
Opened 15 years ago
Closed 15 years ago
Add "tjit-data/trace-monitor" memory reporter
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla8
People
(Reporter: n.nethercote, Assigned: n.nethercote)
References
(Blocks 1 open bug)
Details
(Whiteboard: [MemShrink])
Attachments
(1 file)
|
4.84 KB,
patch
|
dmandelin
:
review+
|
Details | Diff | Splinter Review |
DMD tells me that some things under TraceMonitor are taking a reasonable amount of space. This patch adds a "tjit-data/trace-monitor" reporter for the notable ones.
The size per compartment of this reporter is often around 170KB. An example:
│ │ ├─────362,216 B (00.81%) -- tjit-data
│ │ │ ├──172,224 B (00.39%) -- trace-monitor
│ │ │ ├──148,000 B (00.33%) -- allocators-reserve
│ │ │ └───41,992 B (00.09%) -- allocators-main
So it's not hard for it to get above 1MB when multiple tabs are open. That's not a huge amount, but we gotta keep chipping away at that dark matter.
Attachment #552300 -
Flags: review?(dmandelin)
|
||
Updated•15 years ago
|
Attachment #552300 -
Flags: review?(dmandelin) → review+
|
|
Assignee | |
Comment 1•15 years ago
|
||
Whiteboard: [MemShrink] → [MemShrink][inbound]
|
||
Comment 2•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite?
OS: Linux → All
Hardware: x86_64 → All
Resolution: --- → FIXED
Whiteboard: [MemShrink][inbound] → [MemShrink]
Target Milestone: --- → mozilla8
Version: unspecified → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•