-
Bug
-
Resolution: Fixed
-
Major
-
None
Our deployment of Jenkins with this plugin is currently on an NFS share. In testing a job with this plugin, a file descriptor was apparently left open. We found this out when attempting to delete the test job after it ran. (It was a simple echo job to make sure masking worked as expected, nothing else)
The issue appears to be related to the anonymous sub-class of the LineTransformationOutputStream class returned by the Wrapper class and similar to the bug resolved in JENKINS-28409 for EnvInject. The sub-class needs to clean up it's parent outputstream and the super class on close.
@Override public void close() throws IOException { super.close(); out.close(); }
- duplicates
-
JENKINS-45057 "too many files open": file handles leak, job output file not closed
-
- Resolved
-
- is duplicated by
-
JENKINS-45057 "too many files open": file handles leak, job output file not closed
-
- Resolved
-
-
JENKINS-45946 File Handle Leak
-
- Resolved
-
- relates to
-
JENKINS-28409 EnvInjectPasswordsOutputStream does not close the parent logger
-
- Resolved
-
- links to
[JENKINS-43199] Credentials Binding plugin causes File Descriptor leak
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Priority | Original: Minor [ 4 ] | New: Critical [ 2 ] |
Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
Comment |
[ Marked this as major since after completing the install of the blue ocean plugin (which seems to have been when this bug appeared on my system), I suddenly needed to restart my Jenkins master process every two days to avoid jobs failing with "too many open files" errors. My max open FD limit for jenkins was set to 8196. Initially I worked around this by removing the credentials plugin from some frequently-running jobs. Today, I realized that a rollback of the Credentials Binding plugin to 1.11 was possible in the Plugin Manager, so I tried that. It seems to have stopped the FD leak! What's strange is that 1.11 is displayed as the most recent version on [https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin] Was a newer version pulled from release? Or perhaps the blue ocean installation I did last week pulled in a newer, unadvertised version somehow? ] |
Status | Original: In Review [ 10005 ] | New: In Progress [ 3 ] |
This may potentially cause the same issue for the pipeline variant, but is not used by us at this time.