jenkinsci / jenkinsci/workflow-durable-task-step-plugin

[JENKINS-45873] Subprocess exited with an OOM, pipeline then zombied

Open
#536 1 comment 0 reactions 0 assignees View on GitHub
component:workflow-durable-task-step-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
46
Forks
110
PR merge metrics
No merged PRs in 30d

Description

Over the weekend, two memory intensives jobs were built at the same time. This lead to the linux kernel killing the process in the build step

Jenkins didn't seem to notice that was what happened, leading the the job hanging. Looking at the list of active processes (using ps -ef | grep jenkins) Jenkins didn't have any processes doing anything from what I could tell.

As far as I can tell, pipeline should have seen the fact the subprocess has been terminated?

---
Originally reported by drugcrazed, imported from: Subprocess exited with an OOM, pipeline then zombied


  • status: Open
  • priority: Minor
  • component(s): workflow-durable-task-step-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251212-090250

Raw content of original issue

Over the weekend, two memory intensives jobs were built at the same time. This lead to the linux kernel killing the process in the build step

Jenkins didn't seem to notice that was what happened, leading the the job hanging. Looking at the list of active processes (using ps -ef | grep jenkins) Jenkins didn't have any processes doing anything from what I could tell.

As far as I can tell, pipeline should have seen the fact the subprocess has been terminated?

environment

```
Jenkins ver. 2.71

Pipeline: 2.5
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.