dotnet / dotnet/docs

dotnet-dump subcommand `dumpheap` returning `No CLR runtime found`

Open
#39,774 2 comments 1 reaction 0 assignees View on GitHub
:watch: Not Triaged dotnet-fundamentals/svc
Dominant language
No language data
Stars
4.8k
Forks
6.1k
Avg merge
19h 10m
Merged PRs (30d)
268

Description

### Type of issue

Code doesn't work

### Description

Following the Debug a memory leak in .NET [guide](https://learn.microsoft.com/en-us/dotnet/core/diagnostics/debug-memory-leak), everything seems till work till I go to analyze the dump file:
```
PS C:\Users\Administrator> dotnet-dump analyze dump_20240301_195650.dmp
Loading core dump: dump_20240301_195650.dmp ...
Ready to process analysis commands. Type 'help' to list available commands or 'help [command]' to get detailed help on a command.
Type 'quit' or 'exit' to exit the session.
> dumpheap -stat
ERROR: No CLR runtime found. This means that a .NET runtime module or the DAC for the runtime can not be found or downloaded.
```
I was expecting the dump information presented in the tutorial.

### Page URL

https://learn.microsoft.com/en-us/dotnet/core/diagnostics/debug-memory-leak

### Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/diagnostics/debug-memory-leak.md

### Document Version Independent Id

03f3761e-be31-bae9-6ac7-ad86db389212

### Article author

@tommcdon

### Metadata

* ID: 2913d994-4c72-cc6e-0bd4-ba122ae21753
* Service: **dotnet-fundamentals**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.