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

Issue 848426 link

Starred by 2 users
Status: WontFix
Owner:
█ pmeenan@chromium.org
Last visit > 30 days ago
Closed: Jun 2018
Cc:
█ pmeenan@chromium.org
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2% regression in system_health.memory_mobile at 562148:562152

Project Member Reported by sullivan@chromium.org, May 31 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 31 2018 

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

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


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

android-webview-nexus6
Project Member

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

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

Switch the flag to allow rendering while loadaing in-body CSS for stable. by pmeenan@chromium.org
https://chromium.googlesource.com/chromium/src/+/21154794b8ae44ef571979016fd64b1de23a7cb7
2.037e+07 → 2.059e+07 (+2.194e+05)

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

Comment 4 by pmeenan@chromium.org, Jun 4 2018

Status: WontFix (was: Assigned)
The parser change just changed the timing/sequencing during load.  The levels look to move around a lot and are within previous ranges (and have trended down again).
►

Sign in to add a comment