Like I said, when I delete all the images and fonts, the crash disappears. I’ll have my wife create some placeholder images of approximately the same size, and see if I can reproduce it, then upload the resulting .aia. This clearly has something to do with the way images are being rendered.
The button images are 45x125/250, and 71x125/250. The background image is 666 × 1121. I’m pretty sure my screen would be density 4.
My point is: the app ONLY crashes (with loaded images) when I open and close screens. In fact, it only crashes when I open and close all 4 secondary screens. I can open and close three screens all day long, for 30 minutes, execute code, the whole works, with images loaded and not induce a crash. I can open up the app, do nothing up open and close each screen, in any order, and the moment I attempt to open the 4th screen, it crashes. This strongly indicates to me that something associated with opening a screen is not being properly handled by the “close screen” function, and the functional result is a memory leak that triggers a crash.
Also, unless my phone, no matter what I have running, has exactly the same amount of memory available/unavailable, which I think is unlikely, I’m thinking I’m hitting some kind of memory resource limit not related to the actual available system memory.
Digging through Google, I see quite a number of similar situations, where folks with a moderate number of screens, and a moderate number of images, have similar problems. It’s always corrected by a workaround in the form of reducing from 5 to 2 screens, etc. I’ll stake my twenty years worth of software qa and troubleshooting experience that this is a systemic bug that’s only triggered by a combination of several screens and the use of images embedded in buttons, etc.