sh returnStdout:true leaking deleted file handles

[Kieran Shaw]

Anyone got any thoughts or experience with this: https://issues.jenkins-ci.org/browse/JENKINS-43639?focusedCommentId=302114&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302114

[Michael Kobit]

We see massive file handle leaks on a different Jenkins we have that does not use Pipeline. The leaks were on the build logs. We haven't figured out if it is a plugin or something in Jenkins core and we just dealt with it by restarting Jenkins nighty.

On another instance we use pipelines extensively (and the returnStdout) but haven't ran into file handle leaks hitting the limit. I'll have to check today to see if we are just getting lucky.

On Wed, Jun 7, 2017, 04:39 'Kieran Shaw' via Jenkins Users <jenkins...@googlegroups.com> wrote:

Anyone got any thoughts or experience with this: https://issues.jenkins-ci.org/browse/JENKINS-43639?focusedCommentId=302114&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302114

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2fd3edc0-79d3-4e4c-9f79-611a929b25ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kieran Shaw]

Hi Michael,

Thanks for your reply. I can reliably run that simple little pipeline that uses returnStdout and get a leak. I'm using the latest versions of everything. I find it hard to believe it is a bug in the 'sh' command as it is going to be so widely used, it can't just have been me that comes across it. So I wonder if it is a combination of plugins I've got going on. 

It would be good to hear from more people if they have had any similar problems.