Issue metadata
Sign in to add a comment
|
18.4% regression in media.desktop at 594035:594095 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 6
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1579e83ce40000
,
Oct 6
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/177fa3fce40000
,
Oct 6
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/177fa3fce40000 Fix viz memory dumping by backer@chromium.org https://chromium.googlesource.com/chromium/src/+/6b4ccf33a5d1fe3b216a492ff1ce84269696a480 memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.21e+07 → 1.433e+07 (+2.228e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Oct 6
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1579e83ce40000 Fix viz memory dumping by backer@chromium.org https://chromium.googlesource.com/chromium/src/+/6b4ccf33a5d1fe3b216a492ff1ce84269696a480 memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.21e+07 → 1.433e+07 (+2.228e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Oct 9
This CL just improved instrumentation to record memory allocations that we were previously ignoring. WONT FIX. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 6