Closed Bug 500009 Opened 16 years ago Closed 13 years ago

TM: create a trace memory profiler

Categories

(Core :: JavaScript Engine, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dmandelin, Assigned: dmandelin)

References

Details

(Whiteboard: [MemShrink])

Attachments

(2 files)

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.
Prints out memory usage info for traces.
Nick, should this be repurposed or WONTFIX?
Whiteboard: [MemShrink]
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.

Attachment

General

Created:
Updated:
Size: