Confirmed users
32
edits
MemoryProfiler: Difference between revisions
m
→Objectives
(A memory profiler that focuses on execution flows.) |
m (→Objectives) |
||
| Line 6: | Line 6: | ||
Another common approach is to plot the allocations or the memory usages along the timeline. This gives some intuition of how and when a bulk of objects are allocated. However, it still relies on developers' wisdom, and sometimes chances, to dig out the problematical code snippet. | Another common approach is to plot the allocations or the memory usages along the timeline. This gives some intuition of how and when a bulk of objects are allocated. However, it still relies on developers' wisdom, and sometimes chances, to dig out the problematical code snippet. | ||
This memory profiler is designed to solve the inconveniences and limitations. The goal is to identify the memory eager codes directly. For example, it can show which functions | This memory profiler is designed to solve the inconveniences and limitations. The goal is to identify the memory eager codes directly. For example, it can show which functions retaining most: | ||
SelfSize TotalSize Name | SelfSize TotalSize Name | ||
| Line 17: | Line 17: | ||
851968 851968 t/t.prototype._create (https://marketplace.cdn.mozilla.net/media/fireplace/js/include.js?b=1412710964149:12) | 851968 851968 t/t.prototype._create (https://marketplace.cdn.mozilla.net/media/fireplace/js/include.js?b=1412710964149:12) | ||
or having | or having highest peaks: | ||
SelfHWM TotalHWM Name | SelfHWM TotalHWM Name | ||