New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 912064 link

Starred by 9 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Give More Granular Delete Settings on Logout Options For Shared Chromebook Environments

Reported by amandawu...@gmail.com, Dec 5

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36

Steps to reproduce the problem:
1. For carts of Chromebook shared among many students, set "erase all local user info, settings, and state after each sign out" so that hard drives don't fill up.

2. Deploy 2 Chrome extensions that together are over 100MB to all users
- CoWriter (75MB) https://chrome.google.com/webstore/detail/cowriter-universal-extens/ifajfiofeifbbhbionejdliodenmecna?hl=en
- Snap&Read (42MB) https://chrome.google.com/webstore/detail/snapread-universal/mloajfnmjckfjbeeofcdaecbelnblden?hl=en

3. Watch internet pipe get maxed out as every login to ChromeOS device requires 100MB+ download from google

What is the expected behavior?
Unfortunately the option to delete account data on logout is binary, what would make more sense for shared chromebook environments is to give an option to delete accounts not used in the last X days.  This is how we handle balancing deleting shared user accounts and managing disk space in shared macOS and windows cart environments.

What went wrong?
We quickly maxed out our internet bandwidth after pushing out these 2 chrome extensions that were paid for by our district to help students.  I didn't realize (until yesterday) that extensions could be that big.

Did this work before? N/A 

Chrome version: 70.0.3538.110  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
I work at a university and fully agree with this suggestion. Allowing cached profiles for X amount of days of non-use is exactly how we deal with this issue with Windows-based devices.

For us, we often set it to approximately 1 month of non-use to allow for a full semester. (If a student has not logged in for a full month, the student probably has dropped the class or primarily uses another device.) In other circumstances, we have set it to 1 week. It just depends on the circumstances.
This has me curious and I will be checking my settings on 600+ Chromebook's tomorrow. I force install five extensions and a couple apps to all students. Does this mean multiple copies of the extensions or apps are installed on each device? I'm not aware of any issues with hard drive space, but bandwidth usage may be an issue.
Even though the Extension websites above report 75/42MB, when I actually went to chrome://extensions on a Chromebook, I saw cowriter as 118MB and Snap&Read as 130MB, meaning we were downloading almost 250MB on each login if what chrome://extensions reports is correct.

Since putting the ticket in and entering this crbug, I heard that ChromeOS is supposed to clean out the oldest profiles as space fills up on the drive.  I didn't know that was the case and support didn't tell me.  There's no way for me in the console to run a report on disk usage, right?
Labels: -OS-Windows Enterprise-Triaged OS-Chrome
Owner: naveenv@chromium.org
Status: Untriaged (was: Unconfirmed)
Checked and observed the installed extensions download to a total of 250 MB size mismatching the app size mentioned on chrome webstore (75 and 42 MB).

Google Chrome 72.0.3626.12,11316.14.0 robo.

Please update the Type, if the issue is considered as a feature request.
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment