When using flow-bin, as an example, multiple child processes are spawned during the build that do not get cleaned up when complete. While, in the case of flow-bin, this is a reported bug (wish an open pull request for a fix), the same behavior can be seen with anything that does not clean up after itself.

In the use case that spawned this request, our customer provides Bamboo as a service to their customers and they can opt to use tools such as flow-bin that then leave child processes behind and eventually cuz the agent to run out of memory an crash. It would be preferred if there was a cleanup process to ensure that there are not errant child processes left to consume resources.

—

Workaround:

Since 6.4 "Force stop hanging" is bundled into Bamboo and it is used to kill child processes that hang.

https://confluence.atlassian.com/bamboo/bamboo-6-4-release-notes-946020272.html#Bamboo6.4ReleaseNotes-Force-stopyourhangingbuilds