Vector3GetHashCodeTest AV'ing on Windows release

[stephentoub]

With the latest CoreCLR update, this test is consistently AV'ing on Windows.

  Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
     at System.Numerics.Tests.Vector3Tests.Vector3GetHashCodeTest() in D:\j\workspace\windows_nt_re---37265eab\src\System.Numerics.Vectors\tests\Vector3Tests.cs:line 51

cc: @mellinoe, @CarolEidt

[CarolEidt]

@stephentoub - when I run the tests, this test doesn't seem to run. Has it been disabled? If so, how does one enable it to run the test?

[stephentoub]

Has it been disabled? If so, how does one enable it to run the test?

Yes, I disabled it so that we could update CoreCLR. There's an [ActiveIssue] attribute on the test; just remove it, and it'll start running again.

[danmoseley]

@CarolEidt did you have luck getting this to run?

[CarolEidt]

@danmosemsft Yes,but I haven't got much farther than that.

[danmoseley]

OK! let us know if you need anything on our side.

[CarolEidt]

I was able to repro it and had a possible fix, but after merging with the latest coreclr, it seems to be failing before it hits the previously failing test. I'm continuing to work on it, but may have to pass it to someone else.

[danmoseley]

If it helps -- you can run tests just in one folder by going to the tests folder and doing msbuild /t:buildandtest or /t:test. You can also add [ActiveIssue(1)] on individual tests temporarily but obviously it's probably easier to just comment them out or remove them from the project.

[CarolEidt]

I have a fix for this issue, and the other problem I was running into, which affects only Checked and Debug versions of the JIT.

[danmoseley]

It's great the numeric tests catch these. Do you think https://github.com/dotnet/corefx/issues/15913 is related?

[danmoseley]

dotnet/corefx#15913 can't be related since if I interpret the link in there corectly, it's failing on retail too.

[CarolEidt]

@danmosemsft - I am fixing two issues with dotnet/coreclr#9496. The real issue behind this GetHashCode failure is an issue which causes an AV in retail, and an assert in Checked - though in Checked, if you ran the full set of tests, you would run into the other (Checked/Debug only) AV. So it's possible that dotnet/corefx#15913 is due to the same issue as this.