New issue
Advanced search Search tips

Issue 842620 link

Starred by 1 user
Status: WontFix
Owner:
leszeks@chromium.org
Closed: May 2018
Cc:
leszeks@chromium.org
u...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-21.7% regression in system_health.memory_desktop at 555042:555254

Project Member Reported by ulan@google.com, May 14 2018 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5
android-nexus5X
android-one
android-webview-nexus5X
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 14 2018

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

[parser] Slice the source string where possible by leszeks@chromium.org
https://chromium.googlesource.com/v8/v8/+/2df5e7a7b6d625a69b17d4e11380eed55da3d3e6

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

Comment 4 by leszeks@chromium.org, May 14 2018

Status: WontFix (was: Assigned)
Strange, given that this flag was off by default. The only case where it was accidentally active was I think substrings of JSON strings.

Either way, this is already reverted because of other crashes.
►

Sign in to add a comment