|
||||||||
|
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.
Remember that this by itself does not necessarily, or even probably, indicate that you are seeing
JENKINS-14362; there are numerous other bugs that could cause inappropriate heavy CPU usage. You have to check the master thread dump for threads using Deflater.deflateBytes. In reports I have heard, the typical symptom is that Jenkins starts off running fine, but over the course of a week or so more and more threads get “stuck” in this method (seemingly at random), each consuming 100% of one CPU, so that eventually there are no free processors left to do anything.