13:47:21 <selsta> sech1: they confirmed again that v0.18.3.1 crashes and v0.18.2.2 works.. https://github.com/monero-project/monero/commit/1d1d5fb74cd21821487007959041cd6bc78de9a6 is the only randomx change between these versions
13:47:25 <selsta> looks quite harmless
13:48:03 <selsta> will also ask them to try master build so that we can rule out some antivirus that kills it based on the program hash
14:04:04 <sech1> I found a similar problem https://webcache.googleusercontent.com/search?q=cache:tR9k6-8oU8kJ:forums.purebasic.com/english/viewtopic.php%3Ft%3D69408&hl=en&gl=se
14:04:34 <sech1> "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."
14:04:36 <sech1> Weird
14:08:14 <sech1> Microsoft documentation doesn't say anything about it, so I suspect the real problem is somewhere else
14:12:41 <sech1> I'll try to run 0.18.3.1 monerod under https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/application-verifier
14:21:11 <sech1> maybe some Windows API is called incorrectly somewhere, and other changes in 0.18.3.2 triggered the bug. App verifier can help