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

Issue 874926 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 11
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.3%-2.4% regression in system_health.memory_mobile at 581889:581984

Project Member Reported by tdres...@chromium.org, Aug 16

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=874926

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


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

Android Nexus6 WebView Perf
android-nexus5x-perf
Cc: dpranke@chromium.org
Owner: dpranke@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12c05c56640000

Revert "Reland "[SessionStorageS13N] Enabling mojo SessionStorage by default"" by dpranke@chromium.org
https://chromium.googlesource.com/chromium/src/+/6ef5af6759c379b78b518789649b1e73e8e91a2a
3.773e+07 → 3.886e+07 (+1.136e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: roc...@chromium.org
Owner: dmu...@chromium.org
@dmurph - this was your change, right? I think you resolved this one way or another?
Status: WontFix (was: Assigned)
Yes - I had to disable session storage until I can fix some crashers (where i'm basically onion souping).

Sign in to add a comment