New issue
Advanced search Search tips

Issue 711702 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Quota Manager requires lots of disk space

Reported by d.g.jan...@gmail.com, Apr 14 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Start chrome with profile in tmpfs (with 512MB or less):
google-chrome --user-data-dir=/tmp (with less than 512MB free)
google-chrome --user-data-dir=/run/chrome

What is the expected behavior?
Chrome runs until directory is at least partially full.

What went wrong?
Chrome hangs very soon. (at least in selenium):

"chrome quota_manager.cc(271)] Running out of disk space for profile. QuotaManager starts forbidding further quota consumption"

Did this work before? Yes 56

Chrome version: 57.0.2987.133  Channel: stable
OS Version: Debian
Flash Version: N/A

I suggest to use a quota in relation to the size of the partition, not a large minimum quota. Chrome ran very well with very little space in tmpfs before.
 
Labels: Needs-Triage-M57
Cc: mmanchala@chromium.org
Labels: Needs-Feedback
Jansen@ Since you have mentioned saying he browser is hanging could you please let is know is there any crashes? If yes, Please provide sample crash Id's for further investigation.

Thanks!
No crashes. Anything else I can investigate? I'm doing further debugging right now.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 17 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "mmanchala@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
It's odd. I can no longer reproduce the issue.
It might be that $HOME needs to be inside the tmpfs as well.
I need to correct myself: The chrome version was always 57.0.2987.133.
Status: WontFix (was: Unconfirmed)
As per comment #5 marking this issue as WontFix. Please raise a new Issue if you come across the similar one on any of the latest chrome versions.

Sign in to add a comment