[ https://issues.jenkins-ci.org/browse/JENKINS-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158727#comment-158727 ]
evernat commented on JENKINS-5497: ---------------------------------- As said before, there was activity even in the morning when there was nobody working. Having no more information from the reporter, resolving the issue as incomplete. > OutOfMemoryError: GC overhead limit exceeded > -------------------------------------------- > > Key: JENKINS-5497 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5497 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: java -Xmx1500M -Xms1500M -ea -jar > /home/hudson/hudson/hudson.war > Red Hat Desktop release 4 (Nahant Update 3) > java version "1.6.0_16" > Java(TM) SE Runtime Environment (build 1.6.0_16-b01) > Java HotSpot(TM) Server VM (build 14.2-b01, mixed mode) > Reporter: rickb007 > Priority: Minor > Attachments: 20100129-1521.log.gz > > > This out of memory error occurred early in the morning when nothing much else > was happening and may therefore indicate a memory leak. The server had been > up for five days without any other problem being noticed, and is generally > very reliable. > I have attached the whole log file; the first OutOfMemory error occurs about > half way down and is followed by many others; then other problems arise as a > consequence (these are unlikely to be bugs too). > I have set the priority of this issue to 'minor' because it has not happened > before, even though it crashed the server in this case. (Aside: why's it > called 'priority'? it's a *severity*; don't people know the difference?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira