Mash keeps user wallpapers (unnecessarily?) cached in chrome.
See my change to support wallpapers in Mash:
https://codereview.chromium.org/1984433002/
The preexisting |WallpaperManagerBase::wallpaper_cache_| now keeps a potentially unncessary copy of the wallpaper bitmap in Chrome, since the bitmap is now sent to ash_sysui for rendering in Mash. Previously, the same bitmap data would presumably be used to back these two ImageSkia objects, with Chrome and Ash within the same process.
I'm not sure how easy it'll be to remove the cached image data; nor how that interplays with the login screen's fast switching of wallpapers, or the multi-user simultaneous login cases.
Comment 1 by bugdroid1@chromium.org
, Jun 3 2016