Hello my beloved and occasionally deplorable Noesis users,
The Noesis crash data site receives a high volume of crashes from extremely old versions of Noesis that have been fixed for years. I would think that when you crash, and you get the option to click "Yes" to submit a crash report, it would occur to you to see if the program has been updated to fix your particular crash already. But apparently not. 99% of crash reports come from extremely old versions, I even see a good volume of 3.x ones.
But on top of that, I've included some more useful crash diagnostic info in 4.202, so please make sure you're using at least version 4.202
. Although I obviously can't do anything about crashes happening within third party plugin binaries (which many are), I'd like to make Noesis completely crash-free.
You can update to the latest version of Noesis by using the "Check for Updates" option in the program's "Tools" menu. If you're using a version that's so old that it doesn't have the "Check for Updates" feature (I think that would be 4+ years now), you can download the latest version here
If you're being diligent about updating and submitting the same crash over and over again, feel free to contact me and provide the circumstance and data you're using to get the crash. There's one in particular I've been trying to track that doesn't make a lot of sense from the dump, and seems to indicate some stack corruption (due to a register state that's just been read off of the stack having what appears to be a bad address), but I've been unable to determine where that corruption could've occurred in my offline analysis.
You can make the ads go away by registering