Closed jakobbotsch closed 1 year ago
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas See info in area-owners.md if you want to be subscribed.
Author: | jakobbotsch |
---|---|
Assignees: | - |
Labels: | `untriaged`, `area-NativeAOT-coreclr` |
Milestone: | - |
Cc @LakshanF
I haven't been able to repro this issue but the details strongly resembles the problem ILCcompiler
shows when the runtime provider is enabled via the managed side. The PR #87785 fixed that for NativeAOT applications but the ILCompiler
hasn't been updated yet. This PR #89655 is attempting to do that.
Issues #87739, #8649 has more details.
This should be fixed now.
Recently I've been collecting some regressions/improvements for a JIT change that involves running lots of benchmarks with tracing enabled in the background while I do my regular work. I've noticed two times now the following exception during a normal
./build.cmd
of the runtime, while a benchmark was running with tracing enabled:Both times the build has passed on a retry. To reproduce, try to build/run ILC while running a BDN benchmark with
--profiler ETW
. (Presumably just starting PerfView and running ILC in a loop might have the same effect).For posterity, the exact command I am invoking BDN with in dotnet/performance micro benchmarks was