|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
For those curious or also chasing thread leaks. We troubleshot this issue by taking a hard look at when we saw thread increases, then correlating that to when specific jobs were running, and narrowing the jobs running until we could prove a particular set of jobs always raised the thread count. We did this by standing up a secondary Jenkins master and running experiments to prove the situation.
Once we isolated the jobs, we then analyzed what made those jobs different and narrowed it down to the plugin.
For the record, this behavior can be reproduced by running groovy scripts that spin up threads and don't destroy them before termination as well.