CODEWITHSUNDEEP
javamemory-leaksgarbage-collectionwebsphereout-of-memory
coms
coms

Reputation: 479

OutOfMemory thread dump without GC history

Usually generated thread dump after OutOfMemoryError include information about several last Garbage Collector cycles (GC History section). But I've got OutOfMemory thread dumps without this information. 

1STGCHTYPE     GC History  
NULL           
NULL           ------------------------------------------------------------------------
0SECTION       LOCKS subcomponent dump routine
NULL           ===============================

Environment: IBM WebSphere 7.0.0.19

Someone know why this dump don't have this information? GC didn't start at all?

Upvotes: 1

Views: 484

Answers (2)

Andreas Veithen
Andreas Veithen

Reputation: 9154

In that case you should look at the Snap.*.trc file that the JVM generated together with the dump. It's a binary file, but IBM provides a tool to decode that trace file.

Last time I saw a javacore file without GC history, that was because the OutOfMemoryError was not triggered by heap (or native memory) starvation, but by excessive garbage collection overhead. That was clearly indicated in the trace file.

Upvotes: 2

Mangoose
Mangoose

Reputation: 922

This can happen if your program requested a large enough memory like a large array allocation etc in one go which can't be fulfilled by JVM.

Upvotes: 2

Related Questions