Managing chrome processes

[CanOfBees]

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!

[danielweck]

Hello, I do not know the reasons for zombie Chrome processes when using Puppeteer. Note that Ace uses an old version so perhaps this has since been fixed. Unfortunately we have no plans to upgrade the legacy Puppeteer DeQue-Axe "runner" as this introduces breaking changes and we are focussing on the Electron runner which produces results consistent with the Ace App.
See:
#392 (comment)

Also see Docker configuration that demonstrates how to execute the Electron runner in a headless environment (by using a virtual frame buffer):
#392 (comment)