jenkinsci / jenkinsci/durable-task-plugin

[JENKINS-47971] Leaking Handles to \Device\NamedPipe on slave (Win7, JNLP)

Open
#404 0 comments 0 reactions 0 assignees View on GitHub
component:durable-task-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
30
Forks
101
PR merge metrics
No merged PRs in 30d

Description

Steps to reproduce:

(1) Create a simple, self calling pipeline script 'HelloWorldLoop' and start it:

stage('Foo') { 

    node('test-node') { bat 'echo Hello, World!' }

    build job: 'HelloWorldLoop', wait: false

}

(2) Open Procexp on slave node and watch "Handles"-count rise of the process ip2launcher.exe

 

With every run, there is a new open handle to "\Device\NamedPipe".After ~3000 open handles you can not start even simple GUI applications (cmd, paint, ...). You have to restart the slave agent to go on. I can not open the details in procexp so sorry, I can not provide more details without further instructions (overlooked something obvious? Not used to java-programs...). 

This sounds similar to JENKINS-43199">JENKINS-43199 but this one should be resolved in 2.73.3, shouldn't it?

 

---
Originally reported by peterschneider255, imported from: Leaking Handles to \Device\NamedPipe on slave (Win7, JNLP)


  • status: Open
  • priority: Major
  • component(s): durable-task-plugin
  • label(s): leak, triaged-2018-11, windows
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 2025-12-09

Raw content of original issue

Steps to reproduce:

(1) Create a simple, self calling pipeline script 'HelloWorldLoop' and start it:

stage('Foo') { 
    node('test-node') { bat 'echo Hello, World!' }
    build job: 'HelloWorldLoop', wait: false
}

(2) Open Procexp on slave node and watch "Handles"-count rise of the process ip2launcher.exe

 

With every run, there is a new open handle to "\Device\NamedPipe".After ~3000 open handles you can not start even simple GUI applications (cmd, paint, ...). You have to restart the slave agent to go on. I can not open the details in procexp so sorry, I can not provide more details without further instructions (overlooked something obvious? Not used to java-programs...). 

This sounds similar to JENKINS-43199 but this one should be resolved in 2.73.3, shouldn't it?

 

environment

```
- Jenkins 2.73.3

- Windows 7 Slave, jre1.8.0_151

- Windows Server 2012 R2 Master, jre1.8.0_144

- System Information Master: https://pastebin.com/jNpYPcxR

- System Information Slave: https://pastebin.com/VmfHq5GV

- Plugins: https://pastebin.com/0kafvmwa

- Connection over JNLP

- master and slave run as User, NOT as a Service
```

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.