Issue metadata
Sign in to add a comment
|
5.4%-32.9% regression in media.mobile at 592330:592522 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16dfff97640000
,
Sep 22
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16dfff97640000 Add memory dump support to VizProcessContextProvider. by kylechar@chromium.org https://chromium.googlesource.com/chromium/src/+/e7eca0a627c8289ec11efd27a26df8fe5c81e7e7 1.571e+07 → 2.082e+07 (+5.112e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Sep 24
The alert has 19 graphs related to memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg.
,
Sep 24
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 21