-
Notifications
You must be signed in to change notification settings - Fork 152
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
Enable legacyCorruptedStateExceptionsPolicy #660
Conversation
I agree with your conclusions here - I'd like to hear @rprouse opinion before we merge though. 🙂 |
5224101
to
3bc2e88
Compare
3bc2e88
to
c3cb282
Compare
Awesome! I fixed typos. Guess I was up too late. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. I know some of our users still have partial trust issues tests, so dropping support for it isn't an option right now.
Hi @jnm2 would you happen to remember a link to
We're hitting an AccessViolationException here: and I feel like under some circumstances Assembly.LoadFrom() on .NET Framework can throw AccessViolationException but I can find almost no information about it anywhere, grasping at the straws here |
@KirillOsenkov Yes, see nunit/nunit#3295 (comment) |
Nice, thanks! Looks like it's a different one from ours, ours is in Assembly.LoadFrom(). Also the stack trace one was (fortunately!) fixed for .NET Framework (in fact I think I remember how we fixed it a few years back). |
It does look different. Not sure what to make of this one. Good luck! |
Fixes #336.
Also, in order to fix the intermittent test run hangs investigated at nunit/nunit#3295, at least one of the following things must happen:
This PR gets merged (that was easy, let's go with this one for now 😅)
Microsoft ports the .NET Core fix to .NET Framework 4.7 and 4.8 to fix the race condition that causes stack traces to throw AccessViolationException
NUnit Framework drops support for partial trust (see comment in this PR and Reproducible hang with no user code when shutting down threads nunit#3295)
NUnit Framework implements a watchdog thread to notice the highly bizarre situation set up by the console's current app.config where the console process isn't killed but the NUnit framework test worker thread is killed (see comment in this PR and Reproducible hang with no user code when shutting down threads nunit#3295)