mkeschinger writes:
I checked my errors, all kernel. That was usually linked to software or hardware not releasing memory. so it seems like the update is not handling memory correctly on the older ipads. either because of new feature usage, processor communication or something else. anyone else have that?
I also looked at the error log on my iPad2. Apart from the memory handling that seems to be broken, I also saw that when a process (e.g. Safari) crashes, it is killed by the iOS "watchdog" (error code 0x8BADF00D, Apple engineers have a particular kind of humor). This happens when the watchdog thinks that a process has become unresponsive. This happens when a webpage takes 'long' to load an render. Many websites use 'modern' javascript frameworks, which work well on the latest hardware, but not so good on slightly older (and slower) hardware.
My guess is that on these javascript-heavy pages the iPad2 is a bit slow, and the iOS watchdog expects fast response times like on newer iPads.
The fix for many problems might be as simple as adjusting the watchdog timeout on older iPad models.
This would also explain why some people do not experience issues after applying the other fixes suggested in this forum; They don't visit these 'slow' websites. I usually have crashes on a small set of websites that, for example, have HTML5 video and a lot of javascript.
I have no way to verify if my hunch is correct, and I don't expect that anyone else but Apple can adjust the watchdog timeout.