> On 20 Jul 2015, at 13:45, Allison, Timothy B. <[email protected]> wrote: > > >>> Xmx doesn't limit native memory, so if there's a leak associated with AWT, >>> ImageIO C libraries, or some other JNI library, the process can grow >>> without limit. Such a leak could be due to a bug, or us not calling close() >>> somewhere. > > Got it. Ok. Is there anything I can do to help figure out what's going on?
Try generating a heap dump with -XX:+HeapDumpOnOutOfMemoryError and attaching it to a JIRA issue. You might need to reduce your heap size if it’s huge, to make the dump smaller. — John > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
