Closed
Bug 500009
Opened 16 years ago
Closed 13 years ago
TM: create a trace memory profiler
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dmandelin, Assigned: dmandelin)
References
Details
(Whiteboard: [MemShrink])
Attachments
(2 files)
4.97 KB,
patch
|
Details | Diff | Splinter Review | |
2.24 KB,
text/x-python
|
Details |
OOMs seem to be a major problem for bug 479090, and we don't know why. We need a way to measure the amount of memory being used for traces, which trace trees are using the most memory, the size distribution of traces, and so on.
The first step is to understand how LIR/native memory is managed, and then instrument TM to print a message with memory usage for every trace that is recorded/compiled.
Assignee | ||
Comment 1•16 years ago
|
||
Prints out memory usage info for traces.
Assignee | ||
Comment 2•16 years ago
|
||
![]() |
||
Comment 4•13 years ago
|
||
WONTFIX!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•