gecko-dev/devtools/client/memory/test/chrome/chrome.ini

[DEFAULT]
support-files =
  head.js

[test_DominatorTree_01.html]
[test_DominatorTree_02.html]
[test_DominatorTree_03.html]
[test_DominatorTreeItem_01.html]
[test_Heap_01.html]
[test_Heap_02.html]
[test_Heap_03.html]
[test_Heap_04.html]
[test_Toolbar_01.html]
[test_Toolbar_02.html]
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. --HG-- rename : devtools/client/memory/components/tree-item.js => devtools/client/memory/components/census-tree-item.js 2016-01-13 23:27:30 +03:00			`[DEFAULT]`
			`support-files =`
			`head.js`

			`[test_DominatorTree_01.html]`
			`[test_DominatorTree_02.html]`
Bug 1241070 - refresh dominatortreeitem if expand state changed;r=fitzgen In DominatorTreeItem check props.expanded in shouldComponentUpdate. Added integration/sanity test to check that a node can be collapsed and expanded using mouse events. Added a DominatorTree component unit test to check the expanded nodes are correctly updated. --HG-- extra : rebase_source : 35eeca14296f81b6c8deec1d375b2a98467a460f 2016-01-21 01:21:54 +03:00			`[test_DominatorTree_03.html]`
Bug 1239495 - Label the GC roots in the dominator tree. r=jdescottes Before this patch, we used the underlying root list's C++ type as the label of the GC roots node in the dominator tree. This patch changes that label to "GC Roots", which does not require knowing our implementation of heap snapshots to understand. 2016-01-19 18:29:00 +03:00			`[test_DominatorTreeItem_01.html]`
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. --HG-- rename : devtools/client/memory/components/tree-item.js => devtools/client/memory/components/census-tree-item.js 2016-01-13 23:27:30 +03:00			`[test_Heap_01.html]`
			`[test_Heap_02.html]`
			`[test_Heap_03.html]`
Bug 1219584 - Test that we show the allocations recording hint at the correct times. r=jsantell 2016-01-22 06:15:39 +03:00			`[test_Heap_04.html]`
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. --HG-- rename : devtools/client/memory/components/tree-item.js => devtools/client/memory/components/census-tree-item.js 2016-01-13 23:27:30 +03:00			`[test_Toolbar_01.html]`
			`[test_Toolbar_02.html]`