|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-13617) 64-bit java.lan... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)
- [JIRA] (JENKINS-13617) 64-bit jav... [email protected] (JIRA)

To further debug this issue may I suggest adding the VM flag -XX:-HeapDumpOnOutOfMemoryError and the next time an OOM occurs to upload java_pidpid.hprof for analysis?