New issue
Advanced search Search tips

Issue 874906 link

Starred by 1 user
Status: WontFix
Owner:
dmu...@chromium.org
Closed: Oct 4
Cc:
dpranke@chromium.org
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 781870


Sign in to add a comment

3% regression in system_health.memory_mobile at 581889:581922

Project Member Reported by tdres...@chromium.org, Aug 16 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 16 

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

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


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

Android Nexus6 WebView Perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 17

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/12e89b12640000

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

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

Comment 4 by dpranke@chromium.org, Aug 17

Owner: dmu...@chromium.org
dmurph@, I think this one is you, too?

Comment 5 by dmurph@google.com, Sep 17

Blockedon: 781870
Yup - we can't reland the mojo-ified session storage until we get the onion souping as well. We were crashing due to strange memory corruption bugs. The move to blink should fix this.

Comment 6 by dmu...@chromium.org, Oct 4

Status: WontFix (was: Assigned)
►

Sign in to add a comment