New issue
Advanced search Search tips

Issue 753914 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Track Disk Usage of Chrome in the Wild

Project Member Reported by agrieve@chromium.org, Aug 9 2017

Issue description

We currently track APK size, but don't report how much disk is being used at runtime. We should add UMA for this!

It would essentially do a recursive ls on the app's data directory and report the sum.

Alternatively, we could report the disk usage any time someone visits Chrome's disk usage activity (which itself calculates cache vs non-cache numbers).

In order to make this data actionable, we'd want to break it down into buckets that make sense. E.g. cache vs non-cache makes sense, but are their sub-buckets that would be useful here as well?
 
I think we do already record some disk usage for the profile directory and split out for a bunch of storage types (service worker, media, etc). I think ProfileImpl records some of this
Project Member

Comment 2 by sheriffbot@chromium.org, Aug 13

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment