Multiple crashes using iPad version 3.09.141
Posted: Mon Mar 14, 2011 6:39 pm
Scoring a game today, I had 5 app crashes which I needed to totally reboot my iPad. The screen would just go blank and hang. I could exit out to the iPad home screen, but when I tried to re-enter iScore, it would go back to the same blank screen (no logo/menu page). Once the iPad was rebooted, the game would pick up where it left off, so no data was lost.
I couldn't really figure out any pattern. A few times it crashed when I had to Undo a play, and one time it was with a 3-0 count, and I put in another ball. This is the 9th game on iPad I've scored this season, and this was the first problem I've encountered.
I have iPad OS version 4.2.1 and have 14.5gb free of my 29gb. I was also Webcasting, and after a few re-boots, I turned that off, thinking that might be a problem. However, I still had a few crashes/total reboots after that.
Any suggestions? Do you think it's possible the Push/Fetch features of some other apps may have caused some memory leakage? Just odd that today was the first problems this year. I didn't pre-load any large amounts of data today, as our high-school rosters are loaded early in the year.
Another non-related problem I noticed, which is just an fyi...now that we are in Daylight Savings Time, I noticed the start and end times of our previously played games have had their times shifted 1 hour later.
Thanks!
I couldn't really figure out any pattern. A few times it crashed when I had to Undo a play, and one time it was with a 3-0 count, and I put in another ball. This is the 9th game on iPad I've scored this season, and this was the first problem I've encountered.
I have iPad OS version 4.2.1 and have 14.5gb free of my 29gb. I was also Webcasting, and after a few re-boots, I turned that off, thinking that might be a problem. However, I still had a few crashes/total reboots after that.
Any suggestions? Do you think it's possible the Push/Fetch features of some other apps may have caused some memory leakage? Just odd that today was the first problems this year. I didn't pre-load any large amounts of data today, as our high-school rosters are loaded early in the year.
Another non-related problem I noticed, which is just an fyi...now that we are in Daylight Savings Time, I noticed the start and end times of our previously played games have had their times shifted 1 hour later.
Thanks!