All the SCMs are Git, so it is likely either GitChangeLogParser or GitSCM.computeChangeLog that is responsible for the leak. I suspect the latter; it is not obvious from reading the code that its finally block works in all cases.

Change By: Jesse Glick (31/Mar/14 1:11 PM)
Labels: memory-leak
Component/s: git
Component/s: core
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to