New issue
Advanced search Search tips

Issue 849045 link

Starred by 2 users
Status: WontFix
Owner:
hajimehoshi@chromium.org
Closed: Jul 31
Cc:
hajimehoshi@chromium.org
altimin@chromium.org
haraken@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.2% regression in thread_times.key_mobile_sites_smooth at 563199:563225

Project Member Reported by pmeenan@chromium.org, Jun 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 2 2018 

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

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


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 5 2018

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

Remove PausableTimer from DOMWindowEventQueue by hajimehoshi@chromium.org
https://chromium.googlesource.com/chromium/src/+/cb5d04f327ea4807d4db8dbf2750368673618361
16.63 → 17.99 (+1.36)

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

Comment 4 by hajimehoshi@chromium.org, Jun 6 2018

Cc: haraken@chromium.org altimin@chromium.org

Comment 5 by hajimehoshi@chromium.org, Jun 6 2018 

Now DOMWindowEventQueue is used by various users. I think the situation will change again when we apply appropriate task types for each objects. So let's wait and see.

Comment 6 by pmeenan@chromium.org, Jul 30

Cc: -pmeenan@chromium.org

Comment 7 by hajimehoshi@chromium.org, Jul 31

Status: WontFix (was: Assigned)
As other factors are much bigger now, I'd like to mark this 'won't fix'.
►

Sign in to add a comment