Issue metadata
Sign in to add a comment
|
Recent 5x spike in GPU command buffer usage. |
||||||||||||||||||||||||
Issue descriptionWindows: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=4cd529276cd01ec90463b69351a79961 99.9th percentile: Recent spike around July 5. Previously ~1GB, no 5GB at 99.9th percentile. macOS: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=67c7ac163b14d85b49047704e0cfee2d 99.9th percentile: Used to be 3GB, spiked to 16GB, spike starts July 6. Android: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=950defaa49c4a335b20e79d88d7d4937 99th percentile: Spike on July 6, from 300MB to 1400MB.
,
Jul 12 2017
Regression range: https://chromium.googlesource.com/chromium/src/+log/61.0.3149.0..61.0.3150.0?pretty=fuller&n=10000 One change in this range that seems suspicious is: https://chromium-review.googlesource.com/550664 Watk@, can you take a look and make sure there aren't edge cases where memory isn't being freed or where a huge number of allocations could be cached?
,
Jul 12 2017
Issue 741821 has been merged into this issue.
,
Jul 12 2017
Actually that change is to code that is not currently shipping anywhere.
,
Jul 13 2017
I seem to repro a massive GPU memory leak on linux on a build at 61.0.3150.0 (just open a bunch of tabs and cycle through them), but not top-of-trunk. I will bisect the regression and (if confirmed) the progression, but this might end up as a wontfix.
,
Jul 13 2017
Well, this is a dup of crbug.com/740121 , with the regression at https://chromium-review.googlesource.com/c/558472/ (in the range) and the fix https://chromium-review.googlesource.com/c/566332/ IOW the system works. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by erikc...@chromium.org
, Jul 12 2017Labels: Performance-Memory