This crash seems sporadic, so it's not clear to me whether this is a 1.18 regression. We should probably at least figure out whether there is a memory-corruption problem on this platform before the 1.18 release.
I can see if I can reproduce it, but it looks like an issue that just happens to show up on windows and is actually not really windows specific. It's quite probable that someone from the runtime team proper has a higher chance of finding this problem.
The CL above is likely to fix the crash in 2021-10-29T02:16:47-d6a9af8-2c7cdec/windows-arm64-10.
2021-10-11T21:58:33-18fa840-d973bb1/windows-arm64-10 doesn't contain that pattern so it may or may not be the same error.It could be a memory corruption like the other one earlier then causes the error, or it could be something else.