-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failure: Loader/classloader/InlineArray/InlineArrayInvalid/InlineArrayInvalid.cmd #112330
Comments
Looks like a GC hole exposed by GCStress:
cc @dotnet/jit-contrib |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Failed in: runtime-coreclr gcstress-extra 20250209.1 Failed tests:
Error message:
Stack trace:
|
If this started recently and failures occur during exception handling could be related to #111937. But will need to look closer. |
I have investigated https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-fd5c7483c98a476194/Loader.0.3/1/console.eec09497.log?helixlogtype=result - I was able to catch the crash with time travel debugging (I can share the trace if you need it). I can confirm that this is caused by #111937. We may want to revert this change since it is causing havoc in the runtime tests reliability. The problem is that the GC stackwalk gets lost after
|
Failed in: runtime-coreclr r2r-extra 20250208.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: