-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major
-
Component/s: durable-task-plugin
-
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- 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
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?
Â