I opened Issue 21414 on Jenkins JIRA a few days ago, describing a problem I am having with Jenkins hitting a PermGen space error, causing it to lock up and become functionless. I have since found that I can trigger it on demand, on an otherwise idle, just-restarted, Jenkins JVM, by attempting to view the output from a FindBugs analysis. I have two such analyses, one of about 800 KB in size -- which does not trigger the dump -- and a larger one of about 6.8 MB -- which does. The MaxPerm limits have been set very high, but the error can still be triggered on demand. Could someone please take a look at these two heap dumps, particularly the larger/later one? (See first comment in 21414.) If this is a bug, the right people need to be on it. If this is my own error, it would help to know that. Thank you for your help.
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
