After .NET 6 upgrade, debugger crashes when redirecting from one blazor wasm app to another

[bgriffy]

Describe the bug

On Blazor WASM projects targeting .NET 6, if you run the project in debug mode, the Visual Studio debugger crashes if you attempt to redirect to another Blazor WASM application that also targets .NET 6. The broswer immediately closes.

Here is a quick example I've made on the counter page using the default VS template for a standalone Blazor WASM project:

@page "/counter"
@inject NavigationManager NavigationManager

<PageTitle>Counter</PageTitle>

<h1>Counter</h1>

<p role="status">Current count: @currentCount</p>

<button class="btn btn-primary" @onclick="IncrementCount">Click me</button>

@code {
    private int currentCount = 0;

    private void IncrementCount()
    {
        NavigationManager.NavigateTo("https://bgriffy.github.io/BlazorWasmDebugRepro/");
        currentCount++;
    }
}

If you run this in debug mode, the debugger will immediately crash once you hit the counter button. The application its redirecting to was also created using the default VS template for a standalone Blazor WASM app targeting .NET 6. (https://github.com/bgriffy/BlazorWasmDebugRepro)

I've found that if either of the projects target .NET 5 instead, the debugger runs without issue.

To Reproduce

• Ensure .NET 6 SDK is installed.
• Either create a standalone .NET 6 blazor WASM app, using the default template in VS, and paste the code above in the counter page. Or you can clone my repo: https://github.com/bgriffy/BlazorWasmDebugRepro2
• Run the project in debug mode and click the button on the counter page.

Exceptions

This is the only exception I've seen which I think is related. It pops up in the immediate window in VS.

* Assertion at /__w/1/s/src/mono/mono/eglib/gptrarray.c:117, condition `<disabled>' not met

Further technical details

• ASP.NET Core version: 6.0.100
• I'm using Visual Studio Professional 2022, 17.1.0 Preview 1.1. But I've also reproduced the issue on the current release version.
• Include the output of dotnet --info:

dotnet --info Output

dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.100
 Commit:    9e8b04bbff

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19041
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.100\

Host (useful for support):
  Version: 6.0.0
  Commit:  4822e3c3aa

.NET SDKs installed:
  2.1.700 [C:\Program Files\dotnet\sdk]
  5.0.101 [C:\Program Files\dotnet\sdk]
  5.0.401 [C:\Program Files\dotnet\sdk]
  5.0.402 [C:\Program Files\dotnet\sdk]
  6.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Describe the bug

On Blazor WASM projects targeting .NET 6, if you run the project in debug mode, the Visual Studio debugger crashes if you attempt to redirect to another Blazor WASM application that also targets .NET 6. The broswer immediately closes.

Here is a quick example I've made on the counter page using the default VS template for a standalone Blazor WASM project:

@page "/counter"
@inject NavigationManager NavigationManager

<PageTitle>Counter</PageTitle>

<h1>Counter</h1>

<p role="status">Current count: @currentCount</p>

<button class="btn btn-primary" @onclick="IncrementCount">Click me</button>

@code {
    private int currentCount = 0;

    private void IncrementCount()
    {
        NavigationManager.NavigateTo("https://bgriffy.github.io/BlazorWasmDebugRepro/");
        currentCount++;
    }
}

If you run this in debug mode, the debugger will immediately crash once you hit the counter button. The application its redirecting to was also created using the default VS template for a standalone Blazor WASM app targeting .NET 6. (https://github.com/bgriffy/BlazorWasmDebugRepro)

I've found that if either of the projects target .NET 5 instead, the debugger runs without issue.

To Reproduce

• Ensure .NET 6 SDK is installed.
• Either create a standalone .NET 6 blazor WASM app, using the default template in VS, and paste the code above in the counter page. Or you can clone my repo: https://github.com/bgriffy/BlazorWasmDebugRepro2
• Run the project in debug mode and click the button on the counter page.

Exceptions

This is the only exception I've seen which I think is related. It pops up in the immediate window in VS.

* Assertion at /__w/1/s/src/mono/mono/eglib/gptrarray.c:117, condition `<disabled>' not met

Further technical details

• ASP.NET Core version: 6.0.100
• I'm using Visual Studio Professional 2022, 17.1.0 Preview 1.1. But I've also reproduced the issue on the current release version.
• Include the output of dotnet --info:

dotnet --info Output

dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.100
 Commit:    9e8b04bbff

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19041
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.100\

Host (useful for support):
  Version: 6.0.0
  Commit:  4822e3c3aa

.NET SDKs installed:
  2.1.700 [C:\Program Files\dotnet\sdk]
  5.0.101 [C:\Program Files\dotnet\sdk]
  5.0.401 [C:\Program Files\dotnet\sdk]
  5.0.402 [C:\Program Files\dotnet\sdk]
  6.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Author:	bgriffy
Assignees:	-
Labels:	untriaged, area-Debugger-mono
Milestone:	-

[thaystg]

The published page that you are trying to redirect https://bgriffy.github.io/BlazorWasmDebugRepro is in release mode? If you publish in debug mode it works correctly?

Thanks,
Thays

[thaystg]

@lewing @radekdoulik The thing is that in a published release app it's not linking the "stub" version of the debugger, because of that we are calling mono_wasm_send_dbg_command and the debugger is not enabled, because Blazor didn't enable it, which makes sense because it's a release app. Getting the assert described in the issue.
I can and will protect it on mini-wasm-debugger, but I think we should fix it on published app also.

[radekdoulik]

@thaystg the release should use the stub of debugger component. Do you have a binlog of a build where it doesn't link with the stub?

[bgriffy]

The published page that you are trying to redirect https://bgriffy.github.io/BlazorWasmDebugRepro is in release mode? If you publish in debug mode it works correctly?

Thanks, Thays

Hey @thaystg, thanks for responding. FYI, I published the app (https://bgriffy.github.io/BlazorWasmDebugRepro) in debug mode but it looks like I'm having the same problem.

[radekdoulik]

It looks like the blazor app in VS is not relinking dotnet.wasm at all, so it ends with non-stub debugger component. (from https://github.com/dotnet/runtime/blob/main/src/mono/wasm/runtime/CMakeLists.txt#L16-L18)

When I build the same project on command line with dotnet publish, it is relinked and we get the debugger stub component.

The command line uses Restore and Publish targets, while VS uses

ResolveFrameworkReferencesDesignTime
ResolveProjectReferencesDesignTime2
CollectResolvedSDKReferencesDesignTime
CollectPackageReferences
ResolveComReferencesDesignTime
RazorGenerateComponentDesignTime
BuiltProjectOutputGroup
CollectFrameworkReferences
CollectUpToDateCheckBuiltDesignTime
CollectPackageDownloads
RazorGenerateDesignTime
ResolveAssemblyReferencesDesignTime
GenerateSupportedTargetFrameworkAlias
CollectAnalyzersDesignTime
CollectUpToDateCheckInputDesignTime
CollectUpToDateCheckOutputDesignTime
ResolvePackageDependenciesDesignTime
CollectSuggestedWorkloads
CollectCentralPackageVersions
CompileDesignTime
CollectResolvedCompilationReferencesDesignTime

targets.

@radical @lewing what would be best solution for this?

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Describe the bug

On Blazor WASM projects targeting .NET 6, if you run the project in debug mode, the Visual Studio debugger crashes if you attempt to redirect to another Blazor WASM application that also targets .NET 6. The broswer immediately closes.

Here is a quick example I've made on the counter page using the default VS template for a standalone Blazor WASM project:

@page "/counter"
@inject NavigationManager NavigationManager

<PageTitle>Counter</PageTitle>

<h1>Counter</h1>

<p role="status">Current count: @currentCount</p>

<button class="btn btn-primary" @onclick="IncrementCount">Click me</button>

@code {
    private int currentCount = 0;

    private void IncrementCount()
    {
        NavigationManager.NavigateTo("https://bgriffy.github.io/BlazorWasmDebugRepro/");
        currentCount++;
    }
}

If you run this in debug mode, the debugger will immediately crash once you hit the counter button. The application its redirecting to was also created using the default VS template for a standalone Blazor WASM app targeting .NET 6. (https://github.com/bgriffy/BlazorWasmDebugRepro)

I've found that if either of the projects target .NET 5 instead, the debugger runs without issue.

To Reproduce

• Ensure .NET 6 SDK is installed.
• Either create a standalone .NET 6 blazor WASM app, using the default template in VS, and paste the code above in the counter page. Or you can clone my repo: https://github.com/bgriffy/BlazorWasmDebugRepro2
• Run the project in debug mode and click the button on the counter page.

Exceptions

This is the only exception I've seen which I think is related. It pops up in the immediate window in VS.

* Assertion at /__w/1/s/src/mono/mono/eglib/gptrarray.c:117, condition `<disabled>' not met

Further technical details

• ASP.NET Core version: 6.0.100
• I'm using Visual Studio Professional 2022, 17.1.0 Preview 1.1. But I've also reproduced the issue on the current release version.
• Include the output of dotnet --info:

dotnet --info Output

dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.100
 Commit:    9e8b04bbff

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19041
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.100\

Host (useful for support):
  Version: 6.0.0
  Commit:  4822e3c3aa

.NET SDKs installed:
  2.1.700 [C:\Program Files\dotnet\sdk]
  5.0.101 [C:\Program Files\dotnet\sdk]
  5.0.401 [C:\Program Files\dotnet\sdk]
  5.0.402 [C:\Program Files\dotnet\sdk]
  6.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Author:	bgriffy
Assignees:	thaystg
Labels:	arch-wasm, untriaged, area-Debugger-mono
Milestone:	-