This already bore the signs that it was going to be an interesting one to deal with - especially given where the crash was located at… The first “hail mary” came from the reporter themselves - they managed to ascertain that the crash only happened when the game was ran in single-threaded mode, and in a joint effort we’ve also managed to ascertain that it was also Windows-specific. (I won’t go into the particular details of what a beatmap editor is, as it’s mostly unimportant to the larger topic of this post.)Īs is usual operating procedure, I, along with others, went to try to reproduce the problem on my Ubuntu install, and failed it looked like it was going to be yet another irreproducible, and therefore inactionable, crash report. It all started with yet another GitHub issue, in which a user reported a crash after clicking around in the osu!lazer beatmap editor.

spend a week of evenings looking at why the program you’re looking at apparently entirely fails at arithmetic.įrom the fact that this post exists, you’ve probably guessed that I went for #2.

give up investigating and accept that computers are fickle, unknowable machines, uncontrollable by your puny meat-based mind,.

In a language executing on a VM, with a managed memory model, most bugs are relatively shallow and easy to fix, except for the occasional race if you’re doing multi-threading - so when suddenly it appears that comparison of doubles has stopped working correctly, all bets are off.Ībout the only options available at that point that don’t result in loss of sanity are: Most of the time debugging isn’t really much to write about, especially in C# land.

Osu lazer crasjes