diagnostics icon indicating copy to clipboard operation
diagnostics copied to clipboard

Published 20 hours ago • verified publisher icon dotnet

Error: No CLR runtime found (dump collected with 8.0.0)

Open ivonin opened this issue 1 year ago • 5 comments

Description

Full dump collected with dotnet-monitor can't be properly analyzed with dotnet-dump:

  • dumpheap -stats results in an error: "No CLR runtime found. This means that a .NET runtime module or the DAC for the runtime cannot be found or downloaded."
  • runtimes doesn't indeed show any runtimes.

Configuration

  • The process that the dump is collected from is running inside a container based on mcr.microsoft.com/dotnet/aspnet:8.0-jammy.
  • We run dotnet-dump on Ubuntu 22.04 (jammy).
  • dotnet-dump --version: 8.0.510501+8c08c89a0643d31db91e119b1adb463be3e0ffe5.
  • dotnet-monitor /info output: 8.0.0-rtm.23559.8+8c7f7afdfa9b2472bb1d791e953480f214586ae6; runtimeVersion=8.0.0.

Regression?

We didn't have such problems with .NET 7.

Other information

We can't unfortunately provide the dump in question as it contains sensitive data. The issue is, however, persistent, and we're able to reproduce it 100% of the time (every single dump taken from that environment is un-analyzable on any developer machine).

ivonin avatar Mar 21 '24 20:03 ivonin

@mikem8361

tommcdon avatar Mar 25 '24 15:03 tommcdon

Hello! Is it possible to get any updates on this? Is it likely to be a bug that will get fixed?

ivonin avatar Mar 29 '24 11:03 ivonin

Does the Ubuntu 22.04 you are running dotnet-dump analyze have a .NET 8 or less SDK installed? Or are using the single-file dotnet-dump and/or running in the container with the image?

mikem8361 avatar Apr 10 '24 02:04 mikem8361

The Ubuntu machine we use to analyze the dump does indeed has net8 sdk installed. The same machine can be used to analyze net8 dumps collected from a debian container without issues.

ivonin avatar Apr 18 '24 09:04 ivonin

I need to look into how dotnet-monitor sets up to collect a dump. I tried collecting a dump directly without dotnet-monitor with a simple test app in the above container and the resulting dump worked just fine under dotnet-dump analyze outside the container.

mikem8361 avatar May 20 '24 21:05 mikem8361

Is this issue still reproducible?

mikem8361 avatar Sep 16 '24 17:09 mikem8361

We've moved on to the Debian containers so I can no longer confirm if the problem still persists on Ubuntu. Should I close the issue then?

ivonin avatar Sep 17 '24 09:09 ivonin