An unexpected error has been detected by Java Runtime Environment.
See Comment.
Comments
EVALUATION
It's our conclusion that this Java process is close to the maximum memory limits of the machine, and use of an agent like hprof in this situation is never going to work. The only alternative I see is to use 'java -d64'. I'm closing this bug as will not fix. Sorry.
17-07-2006
EVALUATION
What else do you need to know about swap space on this system?
As I said earlier, swap space is not the problem here. ENOMEM 12 /* Not enough core */
hprof does need a hellofa heap for its own stuff and that is in conflict with my benchmark tunning.
I am afraid hprof aint going to help me do my stuff.
13-07-2006
WORK AROUND
It appears that this Java process needs 64bit, perhaps java -d64 should be used? can it be?
13-07-2006
EVALUATION
Without more data on the swap space of this machine, this bug will likely be closed in the next few weeks.
13-07-2006
WORK AROUND
Try using hprof option depth=0, or if only after cpu information, try cpu=sample.
Or try jmap on the PID.
12-07-2006
EVALUATION
If it's running out of C heap (swap?), and it does indeed need this much space, then there isn't much I can do. The hprof agent needs quite a bit of native library memory (malloc() or C heap) space as it runs.