holsee / holsee/chroxy

Number and weight of chrome instances can grow large

Open
#54 6 comments 4 reactions 0 assignees View on GitHub
help wanted
Dominant language
Elixir
Stars
266
Forks
26
PR merge metrics
No merged PRs in 30d

Description

We have had chroxy running continuously on a machine for a long time - weeks or months.
We noticed that the machine was getting low on memory.

Running `ps -o pid,user,%mem,rss,lim,command --sort %mem ax | less` (on Linux - the equivalent on MacOS is `ps -o pid,user,%mem,rss,lim,command -me`) showed that the processes consuming most of the memory were chrome instances.

Restarting chroxy dramatically reduced both the number and weight of the chrome processes.
Before restart, there were 52 chrome processes using 4.4GB of memory.
After restart, there were 11 chrome processes using 666MB of memory.

I don't know a way to reproduce this situation and, in our case, it's reasonable to restart chroxy periodically during known periods of low activity. But I thought it was worth reporting.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.