Many chromium helper processes remain

[cha0ran]

When I am developing under mac, I found that there are a lot of Chromium Helper (GPU & Renderer) processes left in the background, how should I avoid or close them?

[Nutickets]

We are experiencing this same issue but in our production servers and it's causing our CPU to sit at 90%+

What I've discovered is that this seems to be only an issue from a cold start. If I reboot the server and render a PDF using browsershot, a dozen or so chrome processes spawn and get stuck forever. If I kill those processes manually and then re-render the PDF, it works fine and the processes don't stick around. But if I don't kill the processes, then they stay constantly active and the PDF generation is a bit hit and miss and the whole server becomes sluggish

Any help would be much appreciated

[vatandoost]

These arguments of chromium fixed the issue for me.

$browsershot->addChromiumArguments([
   'no-zygote',
   'single-process',
]);

https://source.chromium.org/chromium/chromium/src/+/main:content/public/common/content_switches.cc;drc=b8152085aa045fe26c428aceaf99b5c83d53caac;l=572

[kriiv]

Curious if this would affect the ability for concurrent instances to run on multiple cores in production?

[Daniel-FDS]

I am experiencing the same think on browsershot version 3. Is there a way to fix this?