Google Chrome processes replicate until they consume the whole CPU

[Diego Cela Fabián]

Hello,

In order to be able to export eazyBI reports and dashboard pages to PDF, we installed Google Chrome on all nodes in Jira Data Center.

However, from time to time we have problems with the Jira instance because the Google Chrome process (/opt/google/chrome/chrome) replicates multiple times in a node, and they consume the whole CPU.

Do you know what could be the cause for it?

Thanks,

[Mary Jennings]

We had the same issue on a Jira DC setup using headless Chrome for eazyBI exports. What helped was wrapping the export command in a script with a timeout to kill long-running Chrome instances, and making sure Chrome runs with proper flags: --headless --no-sandbox --disable-gpu --disable-dev-shm-usage. The last one reduces memory pressure in Docker-like environments.

Also worth checking if exports run in parallel, limiting concurrency helped reduce CPU spikes on our nodes.