Chrome DevTools, OS X: Timeline → Memory → DOM Node Count bug(?) triggered by GPU-accelerated elements : 無料・フリー素材/写真
Chrome DevTools, OS X: Timeline → Memory → DOM Node Count bug(?) triggered by GPU-accelerated elements / Schill
| ライセンス | クリエイティブ・コモンズ 表示-継承 2.1 |
|---|---|
| 説明 | Some progress on this weird behaviour...Applying GPU acceleration via transform: translate3d(0,0,0); appears to confuse the DOM Node Count under Chrome DevTools, Timeline → Memory view when you're looking to confirm the effects of garbage collection.The first staircase shows creation and removal of DOM nodes and JS-DOM references under normal circumstances, followed by garbage collection. Memory and node counts return to their previous values.When the CSS transform is applied to the newly-created elements, something confuses the DOM Node Count graph and it does not drop the nodes even after GC.The Heap snapshot tool (bottom screenshot) does not show evidence of disconnected DOM nodes after the GPU case, so this seems like a problem with the DOM Node Count panel itself.Chrome Canary 32.0.1661.0 on OS X 10.8.5.Update: This appears not to happen under Chrome on an old Windows XP laptop (w/Intel 915 GMA chipset graphics.)I've added a test page for the curious. |
| 撮影日 | 2013-10-05 11:34:52 |
| 撮影者 | Schill |
| タグ | |
| 撮影地 |