-
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 tracing\\eventpipe\\processenvironment\\processenvironment\\processenvironment.cmd #51477
Comments
I'm not sure that the crossgen2 pipeline failures are actually this test failing.
It looks like corssgen2 fails on an assert, but then it still attempts to run the test which seemingly crashes partway through execution. I haven't looked at the dumps yet though. @mangod9 does this type of failure looks familiar to you? As for the gcstress failure, I don't have any hunches. There's no dump to inspect so I'll have to see if this repros. It's attempting to validate the method table pointer for whatever object the GC is inspecting. Either that pointer was null or it failed the validation. runtime/src/coreclr/vm/object.cpp Lines 510 to 514 in 9f10999
The test itself seems to be in the shutdown phase, so this could be during the child process's shutdown. |
hmm.. interesting. Is this an intermittent failure? I would expect field layout asserts would be deterministic. cc @dotnet/crossgen-contrib @trylek @davidwrighton |
For John's comment, the field layout validation error is a runtime crash, not a compile-time crash. One way or another this is super weird as I believe this is the exact bug I was fixing about 1-2 weeks back in As you can see, I used the exact ExtendedSocketException layout to construct the regression test that seems to be passing now. The primary problem quoted by Vincent in the issue description is basically a heap corruption which naturally may occur upon inconsistent field layout calculation but I find it hard to understand how such a crash could occur without previously hitting the field offset verification check. |
Failed again in runtime-coreclr r2r-extra 20210502.1 Failed test:
Error message:
Historical failures of this test has updated in this comment. |
Failed again in runtime-coreclr gcstress0x3-gcstress0xc 20210523.1 Failed test:
Error message:
Historical failures of this test has updated in this comment. |
This continues to fail for Windows x64, Windows x86, Windows arm64 in either GCStress=3 or GCStress=C: |
@josalem, I took a chance too look at this due to the comment about crossgen behavior above. Fortunately it appears to be an entirely different issue. I'm putting together a PR now. |
Run: runtime-coreclr gcstress0x3-gcstress0xc 20210418.1
Failed test:
Error message:
Historical failures of this test:
More failures
The text was updated successfully, but these errors were encountered: