Consider flushing and releasing current context on memory dumps |
|
Issue descriptionContext is https://bugs.chromium.org/p/chromium/issues/detail?id=911124#c7 where eglMakeCurrent with an offscreen surface released some gpu memory in the driver that our test infrastructure measures (memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size under Mapped File -> Devices -> GPU -> /dev/kgsl-3d0) If we flush (finish?) and release the current context, we might get a more reliable reading for our system_health.memory_{mobile,desktop} tests. AFAICT, we expect memory dumps to be heavy weight.
,
Dec 10
It occurred to me that this is probably a bit racey. I don't know where system metrics are collected, but it's probably not viz/gpu process. We'd need to synchronize. |
|
►
Sign in to add a comment |
|
Comment 1 by ccameron@chromium.org
, Dec 7Components: -Internals>GPU>Internals Internals>GPU>Metrics
Labels: -Type-Bug Type-Feature
Status: Available (was: Untriaged)