New issue
Advanced search Search tips

Issue 782210 link

Starred by 1 user
Status: Fixed
Owner:
u...@chromium.org
Closed: Feb 2018
Cc:
mlippautz@chromium.org
mvstanton@google.com
h...@chromium.org
u...@chromium.org
r...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

GC: Concurrent marking temporarily disabled

Project Member Reported by mvstanton@google.com, Nov 7 2017 
Looks like the concurrent marking disable causes this churn
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 7 2017 

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

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


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

chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
linux-release

Comment 3 by mvstan...@chromium.org, Nov 7 2017

Summary: GC: Concurrent marking temporarily disabled (was: 23.7%-573.1% regression in v8.browsing_desktop at 513467:514056)

Comment 4 by mvstan...@chromium.org, Nov 9 2017

Status: Fixed (was: Assigned)
Concurrent marking was re-enabled.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Feb 2 2018

Cc: h...@chromium.org mlippautz@chromium.org u...@chromium.org r...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Fixed)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/13abb5f6840000

Roll clang 315613:317263. by hans@chromium.org
chromium @ c4a8c7b5ff68ad06bdaff91be5170e4da89c3a9f

Reland "[heap] Temporarily disable concurrent marking." by ulan@chromium.org
v8 @ 586067e45dd542a117b67ad66d3b14475d8d571f

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

Comment 7 by gab@chromium.org, Feb 14 2018 

Strolling through opened issues, is this fixed?

Comment 8 by u...@chromium.org, Feb 14 2018

Status: Fixed (was: Assigned)
Thanks, the concurrent marker was re-enable long time ago.
►

Sign in to add a comment