-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
2
-
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.
- mentioned in
-
Page Failed to load
[BAM-19887] Kill child process spawned during build
Description |
Original:
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|https://github.com/flowtype/flow-bin/issues/88] (wish an [open pull request|https://github.com/flowtype/flow-bin/pull/89] 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. |
New:
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|https://github.com/flowtype/flow-bin/issues/88] (wish an [open pull request|https://github.com/flowtype/flow-bin/pull/89] 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 |
Remote Link | New: This issue links to "Page (Confluence)" [ 482565 ] |
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | Original: pse-request | New: bamboo-bugs-grooming pse-request |
Workflow | Original: JAC Suggestion Workflow [ 3019330 ] | New: JAC Suggestion Workflow 3 [ 3603765 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2703761 ] | New: JAC Suggestion Workflow [ 3019330 ] |
Labels | New: pse-request |
UIS | New: 0 |
Support reference count | New: 2 |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |