-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 GC\\Features\\HeapExpansion\\plug\\plug.cmd #63854
Comments
Tagging subscribers to this area: @dotnet/gc Issue DetailsRun: runtime-coreclr outerloop 20220116.2 Failed test:
Error messgae:
or
|
I was looking at the libunwind assert on Friday (using the dump from CI), there is a problem where the remote unwinding code doesn't recognize a managed frame as managed and tries to unwind one more time using the libunwind. That results in 0 instruction pointer and the next call to unwinder fails with that assert due to that. Might be a DACization issue, it is not clear yet. As for the GC issue, here is the call stack at the point of failure, unfortunately all the locals from the interesting frames were optimized out by the compiler.
|
@dotnet/gc I have found I can repro the issue reliably locally in a couple of runs of the |
It is reproducible in debug build as well, so all locals are preserved. I can see that at the crash time, the
|
@dotnet/gc I can share the dump from the debug build run. |
Hi @janvorli, could you please share the debug dump for this? Were you able to repro the failure consistently with regions enabled? |
Failed again in: runtime-coreclr outerloop 20220313.2 Failed test:
Error message:
|
Should be fixed with this: #66696, will leave it open but hoping we dont see these failures in the next few days. |
Closing since this hasnt recurred since the fix. |
Seen today Link. |
@Maoni0 fyi. |
this was not run with my change. it's still this commit 17e435d6 which was from 7 days ago. |
Closing again. |
Run: runtime-coreclr outerloop 20220116.2
Failed test:
Error messgae:
or
The text was updated successfully, but these errors were encountered: