Description
Description
In a Kubernetes environment, we have a process that normally consumes around 3.8 Gi.
When we run dotnet-dump collect
, it causes the process to increase memory usage up to around 7.2 Gi.
Since we have a 6 Gi memory limit for the Pod, dotnet-dump
cannot finish dump generation and fails with a System.IO.EndOfStreamException: Unable to read beyond the end of the stream
exception.
If we set a higher memory limit, dotnet-dump collect
succeeded, approximately doubling the used memory.
Is this expected behavior? Is it possible to make it just save the dump to the file without consuming more memory?
Reproduction Steps
Run dotnet-dump collect --process-id 1
Expected behavior
A dump file is created
Actual behavior
Dump file generation failed and the process may be crashed
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response