O'Reilly logo

Memory Dump Analysis Anthology, Volume 8a by Dmitry Vostokov

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Insufficient Memory (Stack Trace Database)

Once we have seen a sequence of process memory dumps with the largest one almost 4GB. They were all saved from the process with growing memory consumption from 200MB initially. Initially, we suspected process heap Memory Leak (Volume 1, page 356). However, heap statistics (!heap -s) was normal. There were not even large block allocations (Volume 5, page 315). The dumps were also supplied with UMDH logs but their difference only showed Memory Fluctuation (page 35) and not increase. Stack Trace Collection (Volume 1, page 409) revealed one Spiking Thread (Volume 1, page 305) was logging a heap allocation into user mode stack trace database. We could also see that it was Distributed Spike (Volume 6, page ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required