Commit Graph

8 Commits

Author SHA1 Message Date
tdraebing
860f51f12d Bug 1251728 - Make devtools/client/memory/ eslint clean. r=ntim
MozReview-Commit-ID: KlM4HF81imy
2016-12-21 15:21:24 +01:00
Nick Fitzgerald
f2a6ddf449 Bug 1249788 - Implement the census individuals view; r=jsantell
This adds the INDIVIDUALS view state to the memory panel, renames "dominator
tree display" to "label display", and adds a view for listing the individual
nodes in a census group and inspecting each nodes' retaining paths.
2016-04-11 18:04:31 -07:00
Nick Fitzgerald
58e06bb5d1 Bug 1249779 - Remove the "invert tree" checkbox and make inverting a property of the "group by" selection; r=jsantell
Effectively, this moves `inverted` from a global and per-census state, to a
per-`breakdownModel` state. Additionally, a `breakdownModel` is not just a
breakdown spec anymore, but also some extra associated metadata. As such, it has
been split in two and renamed to "censusDisplayModel" and
"dominatorTreeDisplayModel".
2016-03-01 16:20:45 -08:00
Nick Fitzgerald
cc5fc36083 Bug 1249453 - Add arrows from parent to children in census trees; r=jsantell
MozReview-Commit-ID: LFo4jJot2Sr
2016-02-23 14:14:37 -08:00
Nick Fitzgerald
2bd38f8f7e Bug 1246017 - Create the parent map in the HeapAnalysesWorker; r=jimb 2016-02-05 15:11:48 -08:00
Carsten "Tomcat" Book
d479c73778 Backed out changeset 92889fed3b3b (bug 1246017) for xpcshell bustage 2016-02-05 14:06:27 +01:00
Nick Fitzgerald
2a0cd8d15d Bug 1246017 - Create the parent map in the HeapAnalysesWorker; r=jimb 2016-02-04 18:05:00 +01:00
Nick Fitzgerald
07140c5952 Bug 1229229 - Display dominator trees in the memory tool's UI; r=jsantell
This patch overhauls the memory tool's frontend from being in a state of viewing
a snapshot's census (the implicit default) or viewing a census diff (a special
cased kind of thing) to one of three recognized view states: (1) census, (2)
diffing, or (3) dominator tree. The logic surrounding our current view is more
explicit now. View option (3) is the new one, whose introduction required those
clean ups.

Dominator trees are too large to render in full, all at once. Instead, we
eagerly load and render a few levels deep and then incrementally fetch further
subtrees as their parents are expanded in the UI. This means that we get new
Tree component instances across incremental fetches. Before this commit, the
Tree component stored a bunch of state internally (in this.state rather than
this.props) and we would lose focus and expansion state across incremental
fetches. This internal state has been pulled out and made as explicit props,
which are now managed by actions and reducers just like the rest of the state.
2016-01-13 12:27:30 -08:00