Commit Graph

8 Commits

Author SHA1 Message Date
Julian Descottes
4f21c72797 Bug 1315922 - fix react/prop-types issues in client/memory;r=gregtatum
MozReview-Commit-ID: 7o1QhSNOKGi
2017-01-05 17:11:20 +01:00
tdraebing
860f51f12d Bug 1251728 - Make devtools/client/memory/ eslint clean. r=ntim
MozReview-Commit-ID: KlM4HF81imy
2016-12-21 15:21:24 +01:00
Steve Chung
2419c9586a Bug 1253330 - Fix heap-tree-item-field heap-tree-item-name inline style (margin-left) in RTL. r=ntim
MozReview-Commit-ID: Irz2x4P7hx4
2016-08-03 14:24:19 +08: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
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
Jordan Santell
beed2269f7 Bug 1226319 - part 2 - move the common localized strings from the heap view into the frame component itself. Also make the frame component configurable to optionally display the function name and host, and handle scenarios where the column does not exist -- all in preparation for the JIT optimizations view. r=fitzgen 2016-01-22 12:47:03 -08:00
Julian Descottes
d9a54be51a Bug 1239730 - memory table formatNumber/Percent : add space every 3 digits. r=jsantell 2016-01-18 16:24:36 +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