Uncommitted memory 8,61 MBytes (0,54% of reserved) Heap Description This heap is used by msvcr80Ĭommitted memory 1,54 GBytes (99,46% of reserved) Whats more interesting I believe is: Heap Summary Reserved Memory 0 Bytes (0,00% of Total Memory)Ĭommitted Memory 1,67 GBytes (83,75% of Total Memory)
DUMP MEMORY CELLPROFILER FREE
Size of largest free VM block 62,23 MBytesįree Memory 332,87 MBytes (16,25% of Total Memory) We have used the DebugDiag tool to analyze the dump file (the so called Memory Pressure Analyzer), and here's what we got: Report for DumpFM.dmp Now we have a dump file, but how can we locate what caused the excessive memory usage? What we've done so far: It's just one customer dump clearly showing runaway memory consumption. (Note that this realloc was for an operation that allocated a logging buffer and we are not surprised it failed here, because 10MB in one go would be one of the larger allocations that we do apart from some very large pretty unchangeable buffers - the problem itself likely has nothing to do with this specific allocation.)Įdit: After the comments exchange wit Lex Li below, I should add: This is not reproducible for us (at the moment). We therefore conclude that we have a memory "leak" or runaway allocations that either fully exhausted the memory of the process or at least fragmented it significantly enough for the realloc to fail. The dump file was unusually large (1,5 GB - normally they are more like 500 MB).
Opening it in the Visual Studio (2005) debugger shows that we had a crash caused by a realloc call that tried to allocate a ~10MB block. We have received a native (full) crash dump file from a customer.
0 kommentar(er)
