.net core docker memory dump

Cause of .net core docker memory dump

This problem of .net core docker memory dump occurs while using the .net core application in the docker container in the Linux Operating System. The problem with this system is that it consumes a lot of memory space. Now the question arises of how one can get a snapshot of the memory of the .net application. 

Solution

As per the official documentation of .net by Microsoft currently, there is no way to take that snapshot.

Using Windows. For analysis, gcdumpfiles can be inspected in PerfView or Visual Studio. Right now, there is no way. To open one on a non-Windows platform, use gcdumpto.

To compare multiple.gcdumpf files, you can simultaneously open them in Visual Studio.

Using EventPipe, the global .net-gcdumptool gathers garbage collector (GC) dumps from running.NET processes. Garbage collection (GC) memory dumps are produced by starting GC in the target process, turning on special events, and repeatedly creating the graph of object roots from the event stream. This method makes it simple to record GC memory dumps while a process is running. These memory dumps come in handy in the following situations:

Compare the accumulation of things at various moments in time.
Investigating an object’s root (i.e., providing answers to inquiries like “What else refers to this type?”)
Compile broad data on the number of things in the pile.

This command anticipates that the target application and .net-gcdump will share the same TMPDIRenvironment variable on Linux and macOS. The command will expire if that happens.

Also Read: show-doc not working in ruby pry