Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26048

Jenkins no longer cleaning up child processes when build stopped - as of 1.587

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • core, maven-plugin
    • CentOS 6, JRE 7 or 8
      Windows Server 2008 R2, JRE 7 or 8

      Similar to bug 22641, Jenkins no longer cleaning up child processes when a job is stopped.

      To reproduce : Start any job with a surefire execution, once the tests start running, stop the job through the jenkins interface. The surefire process continues to run.

      Just like bug 22641, this behavior started in 1.553, was resolved in 1.565.2, then started again in 1.587.

      Rating this as critical because processes build up eventually causing issues with running out of memory or hitting the nproc limit.

          [JENKINS-26048] Jenkins no longer cleaning up child processes when build stopped - as of 1.587

          Don Bogardus created issue -
          Don Bogardus made changes -
          Link New: This issue is blocking JENKINS-22641 [ JENKINS-22641 ]
          Don Bogardus made changes -
          Description Original: Similar to bug 22641, Jenkins no longer cleaning up surefire executions when a job is stopped.

          To reproduce : Start any job with a surefire execution, once the tests start running, stop the job through the jenkins interface. The surefire process continues to run.

          Just like bug 22641, this behavior started in 1.553, was resolved in 1.565.2, then started again in 1.587.

          Rating this as critical because processes build up eventually causing issues with running out of memory or hitting the nproc limit.
          New: Similar to bug 22641, Jenkins no longer cleaning up child processes when a job is stopped.

          To reproduce : Start any job with a surefire execution, once the tests start running, stop the job through the jenkins interface. The surefire process continues to run.

          Just like bug 22641, this behavior started in 1.553, was resolved in 1.565.2, then started again in 1.587.

          Rating this as critical because processes build up eventually causing issues with running out of memory or hitting the nproc limit.

          Daniel Beck added a comment -

          Is this specific to the Maven project type? Or to freestyle?

          Daniel Beck added a comment - Is this specific to the Maven project type? Or to freestyle?

          Don Bogardus added a comment -

          Only tested it with Maven projects.

          Don Bogardus added a comment - Only tested it with Maven projects.

          Daniel Beck added a comment -

          When you write it started in 1.587, do you mean that it worked in 1.586? Or do you not know when between 1.565.2 and 1.587 it started?

          Daniel Beck added a comment - When you write it started in 1.587, do you mean that it worked in 1.586? Or do you not know when between 1.565.2 and 1.587 it started?

          Don Bogardus added a comment -

          The problem is NOT present pre 1.553, and also NOT present from 1.565.2 through version 1.586.

          So yes, the problem is NOT occurring in 1.586, which is the version we reverted to.

          The problem IS present in 1.553 until fixed in 1.565.2, then it emerged again in 1.587 and continues in the current version.

          Don Bogardus added a comment - The problem is NOT present pre 1.553, and also NOT present from 1.565.2 through version 1.586. So yes, the problem is NOT occurring in 1.586, which is the version we reverted to. The problem IS present in 1.553 until fixed in 1.565.2, then it emerged again in 1.587 and continues in the current version.

          Daniel Beck added a comment -

          If you could help pinpoint this issue, that'd help a lot.

          • Is it only Maven or also Freestyle projects? Test the latter.
          • Is it occurring when building on master, or on slave nodes? Both?

          If you can reliably reproduce this, and know how to build Jenkins, a git bisect would help in pinpointing the responsible commit. Otherwise, a really idiot(me)-proof step-by-step instruction how to reproduce and test for this when compiling e.g. Jenkins itself would be great.

          Daniel Beck added a comment - If you could help pinpoint this issue, that'd help a lot. Is it only Maven or also Freestyle projects? Test the latter. Is it occurring when building on master, or on slave nodes? Both? If you can reliably reproduce this, and know how to build Jenkins, a git bisect would help in pinpointing the responsible commit. Otherwise, a really idiot(me)-proof step-by-step instruction how to reproduce and test for this when compiling e.g. Jenkins itself would be great.

          Don Bogardus added a comment -

          The issue happens on both master and slaves, no difference there.

          For the freestyle test - Would it tell us what we need to know if we created a freestyle project, but configure it to perform the same maven steps?

          Don Bogardus added a comment - The issue happens on both master and slaves, no difference there. For the freestyle test - Would it tell us what we need to know if we created a freestyle project, but configure it to perform the same maven steps?

          Daniel Beck added a comment -

          For the freestyle test - Would it tell us what we need to know if we created a freestyle project, but configure it to perform the same maven steps?

          Yes, that would be ideal.

          Daniel Beck added a comment - For the freestyle test - Would it tell us what we need to know if we created a freestyle project, but configure it to perform the same maven steps? Yes, that would be ideal.

            pi0tras Piotr Zolnacz
            dbogardus Don Bogardus
            Votes:
            39 Vote for this issue
            Watchers:
            39 Start watching this issue

              Created:
              Updated: