We have got a report from our customer who received the following
messages profiling his application:

LH> Exception java.lang.OutOfMemoryError: requested 16 bytes for CHeapObj-new. Out of swap space?

and

LH> Exception java.lang.OutOfMemoryError: requested 314572876 bytes for JvmtiTagHashmapEntry* in /BUILD_AREA/jdk1.5.0_03/hotspot/src/share/vm/prims/jvmtiTagMap.cpp. Out of swap space?

(The entire message is quoted below.)

Looks like massive object tagging causes a problem for an application
with lots of objects.

I found nothing in the JVMTI specification saying about possible
limitation of the number of objects that can be tagged at a time. Is
this a known problem? Is there a way to tweak JVM in command line to avoid the
problem?