Issue metadata
Sign in to add a comment
|
2.2% regression in memory.top_10_mobile at 590823:590876 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 19
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/149dd7c0e40000
,
Sep 22
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/149dd7c0e40000 DelegatedFrameHostAndroid: Fix Screen Capture by fsamuel@chromium.org https://chromium.googlesource.com/chromium/src/+/36be926f766fe3f0cb231123e4b9e6b087aa27e0 1.813e+07 → 1.84e+07 (+2.772e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Sep 30
This was strictly a bug fix so I'm marking this as WontFix. If this caused a regression then we were outputting the wrong thing before. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 19