New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 827142 link

Starred by 2 users
Status: WontFix
Owner:
chiniforooshan@chromium.org
Closed: Apr 2018
Cc:
jam@chromium.org
chiniforooshan@chromium.org
oysteine@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.7%-83.8% regression in loading.desktop at 507715:546145

Project Member Reported by kraynov@chromium.org, Mar 29 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 29 2018 

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

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


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

chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win10
linux-release
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 29 2018

Cc: oysteine@chromium.org chiniforooshan@chromium.org jam@chromium.org
Owner: chiniforooshan@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15a99447440000

Fix startup tracing in renderers by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/f192e8a25e1937336d9cc16f9273b1d13b99530a

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

Comment 4 by chiniforooshan@chromium.org, Apr 17 2018

Status: WontFix (was: Assigned)
The metric was broken (producing no values) since Feb 27, probably because of missing early trace events. My CL fixed it.
►

Sign in to add a comment