|
||||||||
|
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.
In this URL
https://www.dropbox.com/s/rdv1a69t2nau7ep/java_pid79986.hprof
is a second heap dump of about 148 MB, this one triggered by attempting to view a large (6.8 MB) FindBugs warnings output. The PermGen values were set very high, 2048 MB in the creating job, 8192 MB in the JVM. Viewing a companion FindBugs warning output of about 800 KB did not trigger the heap dump.
This can be triggered on demand, on an idle system that has just been restarted. I suspect some sort of memory leak in either the FindBugs plugin or Jenkins itself. I have further verified that I have installed all supporting plugins, and they are up to date. Jenkins itself was just upgraded today to 1.549, with the same result.
As this screen capture shows, a large amount of this memory seems to be consumed by FindBugs.
https://www.dropbox.com/s/1uc6nz2vda6ouae/HeapDump79986_memory_analysis_1.png
If there is something I am doing wrong, please let me know. If there is something wrong with Jenkins or the FindBugs plugin, I hope this shines some light on it.