I’ve been away for quite a while. Was running my dungeon program, and it runs a while, then crashes out of Codea. Are there changes, incompatibilities \, etc., that I should look at?
Thanks!
R
1 Like
@RonJeffries - which version of Codea are you using V3 or V4 ? And what iOS?
@sim @jfperusse - I’ve had occasional issues with Codea that I couldn’t pin down or consistently duplicate. Fealt like Codea stopped as expected, but something still left in memory as problem when restarting it.
Another issue I had was Codea crashing when I ran a ChatGPT produced Codea fireworks example, it slowed down, as expected, when I introduced complexities, but eventually crashed Codea
I’ll post the code for you to check it out when I get onto my iPad later
@sim @jfperusse - attached fireworks demo
V3, iPadOS 26.4.2, upgrading to 26.5 shortly.
Is there any way to see an error message? I don’t see a decent place for a -call, but will keep looking.
Thanks
@RonJeffries - hi Ron, I probably have a copy of your dungeon project but it would take me ages to find it. If you are OK with posting it if you could do so I will check it on my iPads to help try to find any issues.
Hey Ron, good to see you.
I don’t know if you’re using any objective C stuff, but callbacks and other functions that are passed to the objective C APIs can cause total app crashes, apparently because they run on different threads than Codea‘s main draw and touched functions.
I make it a rule to only set flags in those functions and then check the flags inside the regular touch/draw loop if I need them to do anything more complex, especially UI stuff.
Do you have the dungeon project available? I’d love to run it here and profile memory use to see if there is a bug in Codea causing your crash