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

Cleanup leaks Jenkins master memory if node is deleted before cleanup finishes

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      0.34

      Description

      Because the async resource cleanup doesn't check whether the channel it's attempting to send the delete commands over is currently valid, it means that it will keep attempting to delete the directory over and over.  This will cause the GC to hold onto the Channel/machine resources.

      In installations that use the Jenkins cloud feature, nodes that were deleted shortly/immediately after a job being finished will slowly leak resources till they OOM.

        Attachments

          Activity

          Show
          mmitche Matthew Mitchell added a comment - Fixed in https://github.com/jenkinsci/ws-cleanup-plugin/pull/33  
          Hide
          basil Basil Crow added a comment -
          Show
          basil Basil Crow added a comment - Fixed in jenkinsci/ws-cleanup-plugin#33 .
          Hide
          basil Basil Crow added a comment -

          Released in 0.34.

          Show
          basil Basil Crow added a comment - Released in 0.34 .

            People

            Assignee:
            mmitche Matthew Mitchell
            Reporter:
            mmitche Matthew Mitchell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: