Skip to content

Fatal error. System.AccessViolationException #2501

Answered by bradwilson
paultobey asked this question in Question
Discussion options

You must be logged in to vote

This will require the full repro project to understand what's happening here. The stack trace indicates that we're reading the stack of an exception, that's accessing corrupted memory. It's not obvious why an exception object would be corrupted like this without knowing what the code under test is doing. In general, we don't do any unsafe code and/or unmanaged code via interop, so the actual bug is likely living elsewhere (like in the code under test, or in .NET itself).

Please open an issue with a repro project. Thanks!

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by bradwilson
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants