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

Issue 823446 link

Starred by 2 users
Status: WontFix
Owner:
alexilin@chromium.org
Closed: May 2018
Cc:
samans@chromium.org
█ fsam...@chromium.org
m...@chromium.org
alexilin@chromium.org
lizeb@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-66.2% regression in system_health.memory_mobile at 539397:543691

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

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

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

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


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

android-nexus5
android-nexus6
android-nexus7v2
chromium-rel-win10
win-high-dpi
Project Member

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

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

predictors: Skip dns preresolution if a proxy is configured by alexilin@chromium.org
https://chromium.googlesource.com/chromium/src/+/b6e03254a007461585b9b484e620893630f127a8

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

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 24 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14f6fb39c40000

All of the attempts failed. See the individual attempts for details on each error.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 24 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12f6fb39c40000
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Apr 24 2018

Cc: fsam...@chromium.org samans@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1684f639c40000

Surface synchronization: Don't block on the top level renderer on Windows by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/3879527a58c5df0e54fa035bfa5bcba9abca92a0

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

Comment 10 by alexilin@chromium.org, May 2 2018

Status: WontFix (was: Assigned)
No changes after disabling the feature mentioned in c#3. The graphs have restored after this alert, marking as WontFix.
►

Sign in to add a comment