MemoryInfra: system health benchmark should keep track of locked (pinned) ashmem |
|||||
Issue descriptionSee internal discussion in [chrome-gpu] Android Memory and GPU Raster
,
May 4 2016
,
May 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9bb7dd01f68221ad44db5f7afc932157f3bda1cf commit 9bb7dd01f68221ad44db5f7afc932157f3bda1cf Author: catapult-deps-roller <catapult-deps-roller@chromium.org> Date: Wed May 11 20:46:15 2016 Roll src/third_party/catapult/ e166442cd..767a2ce27 (1 commit). https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/e166442cd31d..767a2ce27e51 $ git log e166442cd..767a2ce27 --date=short --no-merges --format='%ad %ae %s' BUG= 608796 TBR=catapult-sheriff@chromium.org Review-Url: https://codereview.chromium.org/1974553002 Cr-Commit-Position: refs/heads/master@{#393051} [modify] https://crrev.com/9bb7dd01f68221ad44db5f7afc932157f3bda1cf/DEPS
,
May 12 2016
The code for this has landed (https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/767a2ce27e51f8357eae74dabe55caed2f76749d). Locked ashmem is now tracked under: memory:{chrome, webview, ...}:{browser, renderer, ..., all}:subsystem:discardable:locked_size
,
Jan 4 2017
,
Jan 4 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by petrcermak@chromium.org
, May 4 2016