Aaron Robinson

@MichalWeczorek Thank you for the simple reproduction. I was able to immediately root out the issue. This has been present since we introduced COM events back in .NET Core 3.1....

@MichalWeczorek and @lukaszch A fix has been checked into .NET 8. I have filed servicing requests for .NET 6 and .NET 7. You can following them at: https://github.com/dotnet/runtime/pull/76035 and https://github.com/dotnet/runtime/pull/76034.

If the native binary that has the COM server isn't there then this makes sense why it would fail, but I don't know enough about the images to say more....

/benchmark list

> BTW is there an easy way to track alloc/free using counters? Would it even be useful? Or would you switch to native profilers at that point? The VS profiler...

> Fixes/helps #40215? Oh wow. Yes! So glad there is an issue filed for this. I'll mark this PR as fixing that.

Benchmark for current changes. ``` | application | baseline | Current | | | --------------------------------------- | ------------------------ | ------------------------ | ------- | | CPU Usage (%) | 64 | 67...

/cc @davidfowl # Benchmarks against .NET 8 ``` | application | baseline | Current | | | --------------------------------------- | ------------------------ | ------------------------ | ------- | | CPU Usage (%) |...

/cc @davidfowl # Benchmarks against .NET 8 ``` | application | baseline | Current | | | --------------------------------------- | ------------------------ | ------------------------ | ------- | | CPU Usage (%) |...

@davidfowl @Tratcher @JamesNK Please take another look. The CI is all green.