12-18-2022, 09:04 AM
By "crash" do you mean it just disappears or hangs?
If you save builds, I'd recommend going back to a build that didn't crash, and comparing what was changed. Another method is to keep stripping out subs one by one until it doesn't crash, and possibly putting the sub back and stripping out enough code to so others can spot it. For instance, if you can strip it down to 300 lines of code, and Steve can't deliver a diagnosis in 30 minutes or less, it's free!
Also, take out _FULLSCREEN and run it windowed alongside Task Manager. See if something you do using the program causes either the CPU or the memory to spike. It's a big help knowing what triggers the crash. It looked like your GOSUB statements were being paired with RETURN statements but double check them to make sure each is returned. Not returning from a GOSUB routine, when frequently used, will cause a stack space leak and lead to a crash.
Pete
If you save builds, I'd recommend going back to a build that didn't crash, and comparing what was changed. Another method is to keep stripping out subs one by one until it doesn't crash, and possibly putting the sub back and stripping out enough code to so others can spot it. For instance, if you can strip it down to 300 lines of code, and Steve can't deliver a diagnosis in 30 minutes or less, it's free!
Also, take out _FULLSCREEN and run it windowed alongside Task Manager. See if something you do using the program causes either the CPU or the memory to spike. It's a big help knowing what triggers the crash. It looked like your GOSUB statements were being paired with RETURN statements but double check them to make sure each is returned. Not returning from a GOSUB routine, when frequently used, will cause a stack space leak and lead to a crash.
Pete