Managing chrome processes
- Dominant language
- JavaScript
- Stars
- 98
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Please provide the following details if possible or relevant:
- [] the version of Ace impacted by the issue (as returned by the `ace -v` command).
`$ ace-puppeteer -v
1.3.2`
- [] the version of Node used to run Ace (as returned by the `node -v` command).
`$ node -v
v18.20.4`
- [] your operating system and version.
Ubuntu 22.04.04 LTS
- [] if the issue is a bug when running Ace: the error message as produced in the log file (you can enable debug logging with the `--verbose` option).
I realize that the issue we're experiencing may be outside of the ace project's purview, but wanted to ask in case there's a possible fix. We're running ace (specifically `ace-puppeteer`) on a headless Ubuntu system. We've noticed zombie chrome processes lingering on the system. Are there any flags we can integrate in the ace-puppeteer call that might help clean up finished procs?
We're not leveraging a containerized approach, but I can see that may be a necessity.
Thanks for your time and help!
Contributor guide
Assessment
This issue has not been assessed yet.