|
||||||||
|
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/groups/opt_out.
@justinharringa: not much made it into 1.509.2, but yes this is a candidate for 1.509.3. The most helpful thing you can do to push it forward is to verify that the fix actually works. Since I have never personally observed the original bug I cannot do that, and we are loath to backport unverified fixes, though I have gotten anecdotal reports that it works.
Verifying the fix would mean confirming in a comment in this issue that (a) you consistently observed this problem (meaning heavy CPU load with thread dumps showing one or more threads stuck in Deflater.deflateBytes) in an earlier build, such as 1.519 or 1.509.2, but (b) you have not seen it recur since updating to a build with the purported fix (1.520 or 1.509.2.
JENKINS-14362-jzlib).