Blazor WASM crashes after a time with Assertion: should not be reached at /__w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91 558006 @ dotnet.6.0.0.csqdfrwtlv.js:1

[carlbm]

Description

After leaving a blazor wasm app open for a length of time (and through sleep/wake cycles) the app will eventually crash (normally 8-12 hours, but can be quicker).

The console looks like:

With Assertion: should not be reached at /__w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91

558006 @ dotnet.6.0.0.csqdfrwtlv.js:1

Reproduction Steps

Create WASM app that has timed interaction with a server, leave for a while.

Expected behavior

The app should continue to work

Actual behavior

The app crashes. There is nothing the user can do except for reloading the page

Regression?

Unsure

Known Workarounds

No response

Configuration

Running on .Net 6
Windows, chrome browser Version 95.0.4638.69 (Official Build) (64-bit)
x64
unsure
tested in chrome

Other information

No response

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

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

Issue Details

---

Description

After leaving a blazor wasm app open for a length of time (and through sleep/wake cycles) the app will eventually crash (normally 8-12 hours, but can be quicker).

The console looks like:

With Assertion: should not be reached at /__w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91

558006 @ dotnet.6.0.0.csqdfrwtlv.js:1

Reproduction Steps

Create WASM app that has timed interaction with a server, leave for a while.

Expected behavior

The app should continue to work

Actual behavior

The app crashes. There is nothing the user can do except for reloading the page

Regression?

Unsure

Known Workarounds

No response

Configuration

Running on .Net 6
Windows, chrome browser Version 95.0.4638.69 (Official Build) (64-bit)
x64
unsure
tested in chrome

Other information

No response

Author:	carlbm
Assignees:	-
Labels:	arch-wasm, untriaged, area-Codegen-AOT-mono
Milestone:	-

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

Issue Details

---

Description

After leaving a blazor wasm app open for a length of time (and through sleep/wake cycles) the app will eventually crash (normally 8-12 hours, but can be quicker).

The console looks like:

With Assertion: should not be reached at /__w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91

558006 @ dotnet.6.0.0.csqdfrwtlv.js:1

Reproduction Steps

Create WASM app that has timed interaction with a server, leave for a while.

Expected behavior

The app should continue to work

Actual behavior

The app crashes. There is nothing the user can do except for reloading the page

Regression?

Unsure

Known Workarounds

No response

Configuration

Running on .Net 6
Windows, chrome browser Version 95.0.4638.69 (Official Build) (64-bit)
x64
unsure
tested in chrome

Other information

No response

Author:	carlbm
Assignees:	-
Labels:	arch-wasm, untriaged, area-GC-mono
Milestone:	-

[lambdageek]

@carlbm Do you have an app that you could share that demonstrates the issue?

[kg]

If you can't share an app, can you describe what the app does? Are there timers running, does it keep sockets open? Does it issue network requests?
When you say sleep/wake cycles do you mean you're sleeping and waking your PC?