New issue
Advanced search Search tips

Issue 888879 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

98% regression in rendering.mobile/percentage_smooth at 592220:592304

Project Member Reported by kouhei@google.com, Sep 25

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=888879

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=5c1b0a13b0cf95ca77243d2f5ba555f70fb18d7a0a954b257d68608569e60397


Bot(s) for this bug's original alert(s):

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: khushals...@chromium.org
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16815c44e40000

gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/2b62fe723102af55ae3c3508d013655647af440b
19.62 → 0.5292 (-19.09)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
I'm reverting the change above. It was landed to check whether it could explain crashes in the gpu process from driver bugs.
Status: Fixed (was: Assigned)
The revert landed. This should be fixed with that.

Sign in to add a comment