Closed maloo closed 10 months ago
It was found in dotnet 7, so 8 RC1 is unrelated to the issue...
In our code base we don't trigger it via OnInitialized, that is just to recreate a second rendering where the value changes from null to not null.
To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document. We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact work.
Thanks for reporting this. There was a rendering related bug that we've fixed in RC2. Not sure if it was the same, though. Could you please try this out with the latest RC2 release and see if you can still reproduce this? Thanks!
Is there an existing issue for this?
Describe the bug
We had some "random" crashes in Blazor rendering internals when doing render tree diffing for some components. It seems to be related to how Blazor handles rendering and diffing of attributes that are null (name, no value). There is some comment in the function that crash trying to say "this is all fine" and referencing a function that doesn't seem to exist anymore. The crash is an
IndexOutOfRangeException
insideAppendAttributeDiffEntriesForRange
.Expected Behavior
No crash inside Blazor rendering for below component.
Steps To Reproduce
Create a new blazorserver-empty project, add the code below in a issue.razor, add Issue component in Index.razor, and run the app. Rendering of Index page will crash inside Blazor rendering engine.
Exceptions (if any)
.NET Version
8.0.100-rc.1.23455.8
Anything else?
No response