>>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? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
