-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Internal CLR error in PEWriter.WritePEToStream #47250
Comments
This appears to be crash during the GC process. Possibly another symptom of #45557
Moving to dotnet/runtime |
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Usually that stack happens when we have a stale pointer to an object. (GC hole, incorrect stack walk, etc). This is x86, I wonder if it's related to the same stackwalk issue I was looking at. cc: @jkotas |
@hoyosjs This is 64-bit x64. It means that it is not the 32-bit x86-specific stackwalk issue you are looking at.
Likely, it is not possible to tell for sure. The fix for #45557 shipped in 5.0.2, but this dump shows that Roslyn is still running on 5.0.0. It is not a good use of time to drill into Roslyn GC crashes on 5.0.0 since they are likely dups of #45557. @jaredpar @RikkiGibson Could you please get Roslyn updated to 5.0.2? If you are still seeing GC crashes once you are on 5.0.2+, we need to repeat #45557 (comment) to root-cause them. |
The test run specifies --platform x86. Is it still an x64 process?
Ah, I didn't know they still used 5.0.0 still. Thanks. |
Yes, the crash dump is x64 without any doubts. I guess that the |
Yes we can move forward to that now that it's released. |
Build log: https://dev.azure.com/dnceng/public/_build/results?buildId=958976&view=logs&j=7817cc08-46f6-529a-b675-9c2d2b016c0b&t=8c177619-984e-58de-5e95-103fbf6e1f0a
Artifacts: (includes dump file) https://dev.azure.com/dnceng/public/_build/results?buildId=958976&view=artifacts&pathAsName=false&type=publishedArtifacts
Also attaching the run logs here but not the dump file due to size.
runtests.log
xUnitFailure-Microsoft.CodeAnalysis.CSharp.Emit.UnitTests.dll.4.log
This occurred in the Test_Windows_CoreClr_Release job. Wondering if we should file this on dotnet/runtime or if we need to first change some configs and keep running CI to try and repro the failure with the diagnostic info they need. @jkotas could you please advise?
The text was updated successfully, but these errors were encountered: