-
Notifications
You must be signed in to change notification settings - Fork 5k
AccessViolationException on macOS in Asn1Tag.TryDecode #101479
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
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
@EgorBo, please take a look. |
Is it possible to build a repro project or at least share a crash dump? I don't think we can diagnose this AVE by only the provided stack trace |
This issue has been marked |
I think this can be closed. I believe the root cause was using |
Description
I suspect this is a JIT issue, similar to #88288. However in this case, turning off ready-to-run does not fix it (as it is already turned off). The stack trace I'm seeing is:
Reproduction Steps
This seems to randomly occur when making lots of TCP connections to the same macOS process. Other than that, I don't have an explicit list of reproduction steps.
If there's a debugger or tool I can attach to the process to get more information as to the cause of the crash, let me know.
Expected behavior
Should not see
AccessViolationException
.Actual behavior
The application crashes.
Regression?
No response
Known Workarounds
No known workaround.
Configuration
macOS 12.6 M1, .NET 8 self-contained trimmed executable (but not ready-to-run)
Other information
No response
The text was updated successfully, but these errors were encountered: