Blazor WASM: "[MONO] * Assertion at ..., condition `<disabled>' not met" (AGAIN)

[PaulSorauer-IPG]

Description

This looks like a gnarly one. 😳

I'm getting an "Error: [MONO] * Assertion at /__w/1/s/src/mono/mono/sgen/sgen-gc.c:2849, condition `' not met" exception raised in the browser in multiple places in my Blazor WASM app.

Anecdotally, this started around the point that I upgraded the .NET version from 8.0.0 to 8.0.2.

I've found a couple of similar threads, but they've long been resolved:

• Assertion at..., condition '<disabled>' not met. #42628
• ILLinker corrupts exception handler ranges for method linker#1507

I was wondering if it was simply an 8.0.2 issue, but to my horror, if I downgrade my .NET version the error still occurs. "And why do you use the word, 'horror'?", I hear you ask? I'm glad you asked...

Even if I'm running .NET 8.00 or .NET 8.0.1, despite cleaning the repo via a git clean -fXd command, rebuilding the solution, clearing the entire browser cache or using different browsers, when I right-click the error in the browser it seems to indicate that it's coming from the 8.0.2 runtime:

I don't understand how I can no reference at all to .NET 8.0.2 with all the previous build artefacts nuked, but the app seems to still be running 8.02.

So long story short, I can't seem to get rid of the exception now it's started. Doesn't matter if I'm running .NET 8.00 or 8.0.1 or 8.0.2.

Can anyone assist me in troubleshooting this further, please? I've absolutely no idea where to go from here.

Cheers.

Reproduction Steps

I have no idea how to create something to preproduce this, considering I don't know where the problem lies and my entire solution is 150K lines of code (which I can't release).

Expected behavior

No Mono runtime exceptions

Actual behavior

Getting Mono runtime exceptions

Regression?

As above, I'm getting this across versions of .NET 8.0.0 - 8.0.2.

Known Workarounds

No response

Configuration

Using Blazor - tried in both Chrome and Edge.

Other information

No response

[ghost]

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

Issue Details

---

Description

This looks like a gnarly one. 😳

I'm getting an "Error: [MONO] * Assertion at /__w/1/s/src/mono/mono/sgen/sgen-gc.c:2849, condition `' not met" exception raised in the browser in multiple places in my Blazor WASM app.

Anecdotally, this started around the point that I upgraded the .NET version from 8.0.0 to 8.0.2.

I've found a couple of similar threads, but they've long been resolved:

• Assertion at..., condition '<disabled>' not met. #42628
• ILLinker corrupts exception handler ranges for method linker#1507

I was wondering if it was simply an 8.0.2 issue, but to my horror, if I downgrade my .NET version the error still occurs. "And why do you use the word, 'horror'?", I hear you ask? I'm glad you asked...

Even if I'm running .NET 8.00 or .NET 8.0.1, despite cleaning the repo via a git clean -fXd command, rebuilding the solution, clearing the entire browser cache or using different browsers, when I right-click the error in the browser it seems to indicate that it's coming from the 8.0.2 runtime:

I don't understand how I can no reference at all to .NET 8.0.2 with all the previous build artefacts nuked, but the app seems to still be running 8.02.

So long story short, I can't seem to get rid of the exception now it's started. Doesn't matter if I'm running .NET 8.00 or 8.0.1 or 8.0.2.

Can anyone assist me in troubleshooting this further, please? I've absolutely no idea where to go from here.

Cheers.

Reproduction Steps

I have no idea how to create something to preproduce this, considering I don't know where the problem lies and my entire solution is 150K lines of code (which I can't release).

Expected behavior

No Mono runtime exceptions

Actual behavior

Getting Mono runtime exceptions

Regression?

As above, I'm getting this across versions of .NET 8.0.0 - 8.0.2.

Known Workarounds

No response

Configuration

Using Blazor - tried in both Chrome and Edge.

Other information

No response

Author:	PaulSorauer-IPG
Assignees:	-
Labels:	arch-wasm, untriaged, area-VM-meta-mono
Milestone:	-

[lewing]

Your inability to get out of the broken state is likely because the workload manifests were updated to 8.0.2 and they do not get overwritten by new installs.

[PaulSorauer-IPG]

Actually we found the cause but I still think this is a strange symptom...

We were overriding an async init but had called the synchronous version of the base init by mistake.

We had a large commit so it was hard to find. How that error caused this is a whole different question.

Leaving this open for visibility in case there's a deeper issue.