sech1: they confirmed again that v0.18.3.1 crashes and v0.18.2.2 works.. monero-project/monero 1d1d5fb is the only randomx change between these versions

looks quite harmless

will also ask them to try master build so that we can rule out some antivirus that kills it based on the program hash

I found a similar problem webcache.googleusercontent.com/sear…ewtopic.php%3Ft%3D69408&hl=en&gl=se

"It looks like the issue is that you cannot move immediately from a shared lock to an exclusive lock? This doesn't make a lot of sense to me, but when I changed my code to using exclusive locks only, the problem seems to have disappeared."

Weird

Microsoft documentation doesn't say anything about it, so I suspect the real problem is somewhere else

I'll try to run 0.18.3.1 monerod under learn.microsoft.com/en-us/windows-h…rivers/devtest/application-verifier

maybe some Windows API is called incorrectly somewhere, and other changes in 0.18.3.2 triggered the bug. App verifier can help