Confirmed users
83
edits
DevTools/Planning/Performance/Details: Difference between revisions
Jump to navigation
Jump to search
DevTools/Planning/Performance/Details (view source)
Revision as of 23:14, 22 November 2013
, 22 November 2013→Performance Overview
| Line 26: | Line 26: | ||
</ul> | </ul> | ||
Here is an example of a memory leak timeline design that would allow exploring for memory leaks: | Here is an example of a "memory leak timeline" design that would allow exploring for memory leaks: | ||
<ul> | |||
<li>Objects are grouped: examples include grouping by various object roots, by event handlers, by DOM, and by constructors. | |||
<li>Each group has a horizontal timeline where creation of objects is represented by a color with an intensity proportional to the number of objects created per unit of time (usually a frame), and another color and intensity is represented for GC'd objects. | |||
<li>On the right is a detailed count summary for the group. | |||
<li>Since we can't tell how many objects are really in use, but we can only count with respect to time, we pick a "null time bookmark" which defaults to the far left of the timeline but can be moved by the user if desired. (Important for dynamic recording.) (It would also be nice to have a "reload" marker so that the user can choose to reload the page and get an exact count relative to the reload event.) | |||
<li>Two sliders can be used to depict object sizes. If both are selected, the diff is shown, if only one is selected, total# is shown with respect to null time bookmark. | |||
<li>Detailed view below the timeline shows the object list and associated object tree with the selected object grouping (usually a type of root.) | |||
</ul> | |||
<p> | <p> | ||
[[Image:MemoryView.png|center|thumb|980px]] | [[Image:MemoryView.png|center|thumb|980px]] | ||