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

Issue 823502 link

Starred by 1 user
Status: Fixed
Owner:
samans@chromium.org
Closed: Jun 2018
Cc:
samans@chromium.org
█ fsam...@chromium.org
m...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

27.1%-40.3% regression in system_health.memory_desktop at 543825:543914

Project Member Reported by m...@chromium.org, Mar 19 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 19 2018 

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 20 2018

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

content: Only drop fallback if sized changed while hidden by samans@chromium.org
https://chromium.googlesource.com/chromium/src/+/747b7b5664f539ce4f58f4aba37c462d1d5c834a

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

Comment 4 by samans@chromium.org, Jun 13 2018

Status: Fixed (was: Assigned)
We were destroying surfaces that we shouldn't have so of course the memory usage was lower.

Comment 5 by samans@chromium.org, Jun 13 2018 

 Issue 823499  has been merged into this issue.
►

Sign in to add a comment