Fatal error. System.AccessViolationException #2501
-
xUnit 2.4.1 I'm getting intermittent crashes of a large, multiple test assembly, test set (1800+ tests, 4 test assemblies, 150 tests creating/using/dropping SQL Server databases):
The point in the process at which the test crashes varies and there does not appear to be a correlation with any individual tests which are in process. Any command-line switches that would deliver better information? Any other suggestions? I'll try to set up memory dumps when it fails... Thanks, Update 1: Here's a sample dump file when the error occurs: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
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! |
Beta Was this translation helpful? Give feedback.
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!