New issue
Advanced search Search tips

Issue 862236 link

Starred by 1 user
Status: WontFix
Owner:
sunn...@chromium.org
Closed: Jul 11
Cc:
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

∞% regression in mean_frame_time_renderer_compositor at 571452:571551

Project Member Reported by 42576172...@developer.gserviceaccount.com, Jul 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 10 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=862236

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 11

Cc: grunell@chromium.org
Owner: grunell@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/148d42aaa40000

Revert "cc: Post task on mojo begin frame to mitigate begin frame flood" by grunell@chromium.org
https://chromium.googlesource.com/chromium/src/+/5a7793c70583c57d485709a21c38bcc1145e272c
36.81 → 409.8 (+373)

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

Comment 4 by grunell@chromium.org, Jul 11

Cc: -grunell@chromium.org
Owner: sunn...@chromium.org
Assigning to sunnyps@, who wrote the CL I reverted. Can you see if this alert is related?

Comment 5 by sunn...@chromium.org, Jul 11

Status: WontFix (was: Assigned)
Not a real regression since this is due to a revert. Although the CL that was reverted was supposed to make things better, 0 cpu time for renderer compositor probably means that there was a bug (probably the same that caused the revert).
►

Sign in to add a comment