Issue metadata
Sign in to add a comment
|
122.6% regression in media.desktop at 583935:583947 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14eda09a640000
,
Aug 21
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14eda09a640000
,
Aug 23
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12c6b05a640000
,
Aug 23
📍 Found significant differences after each of 3 commits. https://pinpoint-dot-chromeperf.appspot.com/job/12c6b05a640000 Remove GpuProcessHost::RequestGPUInfo() by mohsen@chromium.org https://chromium.googlesource.com/chromium/src/+/4bb8218b7d5a8553500fd93ce0fdfa349e15e536 101.6 → 58.21 (-43.38) Roll src/third_party/pdfium 136342d950c9..9faabc5fc371 (1 commits) by pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/75077f616e732d8f1d9e8753fdab63cbde67906d 58.65 → 63.53 (+4.878) Use ContainerNode& instead of ContainerNode* as a parameter of InsertedInto by hs1217.lee@samsung.com https://chromium.googlesource.com/chromium/src/+/9cfd653c560be7e2ef8333ad580d4c54d7563b2d 63.53 → 57.85 (-5.68) Understanding performance regressions: http://g.co/ChromePerformanceRegressions |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 21