cc/trees allocates too much when loading inline SVG |
|||
Issue descriptionInvestigating the memory of SVG images I found that a page with 1000 <svg><rect></svg> entries allocates ~700KB in cc/trees. My testcase is here with 1000 <svg><rect></svg> entries: https://output.jsbin.com/bijoyaf/quiet Using --enable-heap-profiling and about:tracing with memory-infra enabled, I found this page allocates 689KB (malloc) in cc/trees.
,
Jul 20 2017
I found most of this memory is blamed on cc/trees because that's where the paint op buffer is created. This is primarily the display item list memory, and 700KB is reasonable. I have a speculative patch up for not doing some compositing work when compositing is disabled: https://chromium-review.googlesource.com/c/580328. I also found we run a timer for cursors in SVGImages. I'll look into disabling that.
,
Jul 20 2017
,
Jul 20 2017
I found the compositing update code has side effects and isn't easy to disable when accelerated compositing is not enabled. |
|||
►
Sign in to add a comment |
|||
Comment 1 by schenney@chromium.org
, Jul 13 2017