Issue metadata
Sign in to add a comment
|
5.6%-185.2% regression in media.desktop at 541400:541500 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 12 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12d2cf6e440000
,
Mar 12 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/12d2cf6e440000 predictors: Allow port in urls. by alexilin@chromium.org https://chromium.googlesource.com/chromium/src/+/48e8746b747754f10a3494523b07f0a492ec659d Add support for mid ligature position on ShapeResult by fserb@chromium.org https://chromium.googlesource.com/chromium/src/+/6e39ad9cab1d1907952309b7612edc2436762396 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 13 2018
,
Mar 13 2018
The regression is caused by my change, suspecting slow Windows I/O, investigating.
,
Mar 13 2018
Thanks for taking this on, alexilin@. > Add support for mid ligature position on ShapeResult by fserb@chromium.org https://chromium.googlesource.com/chromium/src/+/6e39ad9cab1d1907952309b7612edc2436762396 has been reverted.
,
Apr 5 2018
The regression was fixed at the point #546940 (https://chromium-review.googlesource.com/c/chromium/src/+/980876), confirmed by the graphs. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 12 2018