Oh, I see you mean exiting gracefully with an error instead of crashing. That's different, my bad. But not so different though, because telling a user your gam

Oh, I see you mean exiting gracefully with an error instead of crashing. That's different, my bad. But not so different though, because telling a user your game/app can't run anymore because <insert pleasant looking reason here> doesn't help and the user can hardly do anything to help give the app a higher chance to run. Of course they can start Safari, close all the tabs etc, but it is (1) tedious and (2) many users wouldn't know how to do it (3) again destroys the experience. Also, try to catch the error may not work in practice. It will work sometimes, but there's really no guarantee how much time you have to save the current state, and show a nice error because the app is shutdown. The irony is that the environment uses reference counting to allow better control of memory yet there is this limitation. Or maybe it had to use reference counting because of this limitation. Still it's a pretty nice platform to code for, it's just us developers asking for more :)