-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Thumbnail generation leaves many defunct chrome processes #297
Comments
Studiosity/grover#102 looks like a similar problem, which is where I found the above link. |
As a workaround I'm restarting the job processor container several times a day. |
@simonbaird you found any solution for the defunct chrome processes ? |
@jandresrodriguez Nope. I'm still restarting containers every few hours to clear them. |
|
Not sure if this is still happening. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
dumb-init
might be relevant, see here.Could also perhaps try to move the entire thumbnail generation into its own container.
The text was updated successfully, but these errors were encountered: