WasmExtension.vsix breaks VS2022 .NET debugger

Version: 0.22 and older

Frequency: Consistently

Severity: Low

Context: Visual Studio debugger

Bug description: With the Wasm Extension installed into Visual Studio 2022, I’m no longer able to debug .NET applications which are completely unrelated to MSFS. Attached is a basic Hello World .NET project straight from VS wizard and trying to debug it generates an “Your app has entered a break state, but no code is currently executing that is supported by the selected debug engine” message. The output window shows the following errors:

[Wasm Extension][Error] Could not read top frame info at addr 2285786497024, offset 14829735431805717965
[Wasm Extension][Error] DataItem has not been well initialized
[Wasm Extension][Error] ProcessWasmFrame failed
[Wasm Extension][Error] Could not read top frame info at addr 2285786497024, offset 14829735431805717965
[Wasm Extension][Error] DataItem has not been well initialized
[Wasm Extension][Error] ProcessWasmFrame failed

Disabling or removing Wasm extension fixes the issue.

Repro steps:

Use the attached project and put the breakpoint as shown. Launch debug.

Attachments:
ConsoleApp1.zip (244.9 KB)

Hello @some1

I moved this bug report to the SU13 flighting section.

Thank you for reporting this, we are working on a fix.

Regards,
Sylvain