New issue
Advanced search Search tips

Issue 844072 link

Starred by 3 users
Status: WontFix
Owner:
sande...@chromium.org
Closed: May 2018
Cc:
sande...@chromium.org
npm@chromium.org
tmathmeyer@chromium.org
chiniforooshan@chromium.org
yuweih@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

54.9%-79.8% regression in media.desktop at 558788:558996

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

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

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

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


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

chromium-rel-mac11-pro
chromium-rel-mac12
Project Member

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

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

[media] Trace all queued images in VTVDA::OnMemoryDump(). by sandersd@chromium.org
https://chromium.googlesource.com/chromium/src/+/dfe42457393ccc5f445c6cbfd225e99e29fae6af

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

Comment 4 by sande...@chromium.org, May 17 2018

Status: WontFix (was: Assigned)
Measuring this memory was the purpose of the CL.

Comment 5 by sande...@chromium.org, May 17 2018

Cc: chiniforooshan@chromium.org
 Issue 844130  has been merged into this issue.

Comment 6 by sande...@chromium.org, May 18 2018

Cc: yuweih@chromium.org npm@chromium.org
 Issue 844627  has been merged into this issue.

Comment 7 by sande...@chromium.org, May 20 2018 

 Issue 844666  has been merged into this issue.
►

Sign in to add a comment