|
||||||||
|
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/groups/opt_out.
Finally managed to reproduce. Create three freestyle jobs, each of which triggers the other two in a post-build step, and start one of them on a Jenkins instance with two executors. After you get to around build #10 of each, the
JENKINS-14814fix kicks in and prunes the very old causes—but the breadth of the cause tree causes it to be unmanageably large at that depth.0626f28 did not really introduce the problem, it just made it more visible and added new symptoms. Even without that, build.xml runs to over 3Mb per build, which is very expensive to parse during startup and requires a great deal of heap to retain.