out of swap space?

This advice may make the problem worse - the error he/she is seeing stems from a failure to allocate from the native heap so increasing the size of the java heap will reduce the virtual memory available for the native heap.

The original posting doesn't give much information. Since this forum is for JVM TI issues then maybe he/she is having this problem with a JVM TI agent. It would be good to get more information (like version numbers, operating systems, etc.). If the issue is with a memory profiler then perhaps it is tagging all objects (which is expensive). There is some improvements in this area in Java SE 6 and some debugging flags to help too.

alan.batemana at 2007-7-15 3:47:25 >