CreateDump may use too much memory

[leculver]

Our partner team reports that on Linux, createdump can take up to 150mb of memory usage in a Linux container environment and may cause the container to OOM. This is surprising because createdump mostly works on small chunks of memory when reading from a process and writing to a dump.

I have not tried to reproduce this myself. This work item is to investigate this issue and see if we can reproduce it, if not we should reach out to Remi for more details.

Note this is distinct from #71472. #71472 asserts that the target process increases in size, whereas this issue is tracking whether createdump itself is using too much memory.

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Our partner team reports that on Linux, createdump can take up to 150mb of memory usage in a Linux container environment and may cause the container to OOM. This is surprising because createdump mostly works on small chunks of memory when reading from a process and writing to a dump.

I have not tried to reproduce this myself. This work item is to investigate this issue and see if we can reproduce it, if not we should reach out to Remi for more details.

Note this is distinct from #71472. #71472 asserts that the target process increases in size, whereas this issue is tracking whether createdump itself is using too much memory.

Author:	leculver
Assignees:	mikem8361
Labels:	area-Diagnostics-coreclr, dotnet-dump
Milestone:	-

[mikem8361]

I've been investigating this and figured out why createdump's memory usage is increasing so much but I don't have any fix yet. I haven't come up with any work around other than creating "full" dumps or any fix especially one that will fit in our 7.0 schedule.