Issue metadata
Sign in to add a comment
|
1.8%-1643.5% regression in xr.browsing.wpr.static at 589617:589704 |
||||||||||||||||||||||||||||
Issue descriptionBisect points to https://chromium-review.googlesource.com/1205202 as the culprit. The absolute increase is at most ~150 KB though, so it's probably safe to just eat the increase.
,
Sep 12
,
Sep 12
Looks like there are actually a couple of ~30 MB regressions
,
Sep 12
ya just saw it. looking at it.
,
Sep 28
I looked at the failing tests. The increase in memory is not a bug in this case. The code without my CL was buggy. Gpu services were backgrounded and transfer cache was cleaned whenever the CompositorImpl/SurfaceView was destroyed or not visible. This was incorrect behavior. My CL fixed it to only background the gpu services and clean cache when the whole app/browser is minimised/backgrounded. Since the trace is recorded before the browser is closed/backgrounded, my CL shows more memory occupied due to transfer cache not being cleaned up until the browser gets backgrounded. |
|||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 12