IBookstore, App Store, iTunes Store crash.

Question

I've been experiencing this for quite a while and have just been putting up with it.  When browsing any of the Apple Stores (iBooks, App Store, iTunes) they ALWAYS crash.  I'll get no more than 2 screens when the store crashes.  Upon relaunch of the app, it takes me back to an older session so I have to renavagate to the point where I last was and of course this causes the app to crash again.  It always seems to happen when the app is loading a new screen.
I have gen 1 iPad wifi 32 GB, using OS 5.1.1, with approx 5 GB free space.  I thought it might be free memory problem, so I unloaded a lot of old apps that I don't use and tried browsing the stores with about 10gb free space, but they still crash.  I have restarted and shut down and that does not seem to help either.
Does any one know what could be causing this?
Thank you for any help!
David

Answer 1

I had the exact iPad 1 that you have. I have since purchase the iPad 3 and my daughter is using the original iPad. I had some issues with iOS 5, low memory warnings galore. IOS 5.1.1 seemed to clear most of these issues up for me on that iPad. However, this forum had its fair share of users talking about all sites of memory issues with iOS 5.
As I would always assume in instances like this, we were in the minority, and that most users did not experience these types of problems with their iPads when they jodated to iOS 5. But when you are one of the users that is having issues, the fact that you're in the minority doesn't make it any easier to swallow.
Anyway, my belief is that iOS 5 stretched the original iPad processor to its absolute limits and since no update beyond iOS 5.1.1 was ever released for the original iPad, it became an instance of "it is what it is" and for those of us that had those issues, we had to look for workarounds in order to continue to use the device.
Like I said iOS 5.1.1 helped a great deal, but I still had to keep an eye on what apps I was running and even though iOS is supposed to handle those memory issues without user input, it clearly didn't do what it was touted to do in that regard ... At least for some of us.