Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome sometimes fills the disk with temporary profile directories #440

Closed
jugglinmike opened this issue Feb 7, 2018 · 7 comments

Comments

@jugglinmike
Copy link
Collaborator

commented Feb 7, 2018

This problem occurs very infrequently, so we don't know the cause of this yet. It has been confirmed by the Chrome team and potentially resolved. (@mattl: could you add a reference to the bug report you found?)

Workaround: Reboot the machine

@mariestaver mariestaver added this to To Do in WPT Dashboard Feb 9, 2018

@mariestaver mariestaver moved this from To Do to Backlog (future sprints) in WPT Dashboard Feb 9, 2018

@mattl mattl moved this from Backlog (future sprints) to To Do in WPT Dashboard Feb 12, 2018

@mattl mattl self-assigned this Feb 12, 2018

@mattl mattl moved this from To Do to Backlog (future sprints) in WPT Dashboard Feb 12, 2018

@mattl mattl moved this from Backlog (future sprints) to To Do in WPT Dashboard Feb 12, 2018

@mattl

This comment has been minimized.

Copy link
Contributor

commented Feb 12, 2018

@jugglinmike

This comment has been minimized.

Copy link
Collaborator Author

commented Feb 16, 2018

Experiencing this again today.

https://bugs.chromium.org/p/chromium/issues/detail?id=765398 is a more relevant bug report (and still open)

@jugglinmike jugglinmike changed the title Chrome sometimes fills the disk with small files Chrome sometimes fills the disk with temporary profile directories Feb 16, 2018

@mattl

This comment has been minimized.

Copy link
Contributor

commented Feb 16, 2018

@mattl

This comment has been minimized.

@mariestaver mariestaver moved this from In progress to Done in WPT Dashboard Feb 20, 2018

@mattl mattl closed this Feb 20, 2018

@mattl mattl reopened this Mar 5, 2018

WPT Dashboard automation moved this from Done to In progress Mar 5, 2018

@mattl

This comment has been minimized.

Copy link
Contributor

commented Mar 5, 2018

Deleting these files in the browser-runner.sh script before a run doesn't seem to work. Not sure if deleting them after a run would work either. Rebooting the machine after each run may be the solution.

@mattl mattl moved this from In progress to To Do in WPT Dashboard Mar 12, 2018

@mariestaver mariestaver moved this from To Do to In progress in WPT Dashboard Mar 12, 2018

@mattl

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2018

For now, rebooting this machine after the run as part of browser-runner.sh.

Make a patch to include this into the version of browser-runner.sh in master (and deploy it, via Ansible to current 4 machines)

@jugglinmike

This comment has been minimized.

Copy link
Collaborator Author

commented Apr 5, 2018

We currently handle this case with a dedicated build step which follows every "chunk" execution. These segments of the full WPT suite are small enough (and the workers' disks are spacious enough) to accommodate any "leaked" temporary files. In the future, I would be interested in more generic solutions (e.g. via full system restart or via usage of disposable LXC containers), but the current solution appears to be sufficient for our immediate needs.

@jugglinmike jugglinmike closed this Apr 5, 2018

WPT Dashboard automation moved this from In progress to Done Apr 5, 2018

@boazsender boazsender removed the in progress label Apr 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.