Hmm, sounds like caches of JITted script may be the culprit. Real-world upgrade scenarios are difficult to automate and cover but this shouldn't have slipped by Apple QA. Sigh.
That indeed sounds likely. Delving into the crash report a bit deeper, I saw it had "JS VM Gigacage (reserved)" of over 60GB (WTF?), and it seems like JIT cache and JavaScriptCore's scavenger thread related. Could be that the WebKit in 15.3.x was a bit more fault-tolerant of corrupted cache (I did indeed notice some JS-heavy sites having hiccups lately on 15.3.x, whereas the system in 15.4 just SEGFAULTed outright on corrupt data (which shouldn't be there in the first place, but well). Still, it was a
EXC_BAD_ACCESS (SIGSEGV) & KERN_INVALID_ADDRESS, which shouldn't have slipped by their QA indeed. That sounds a bit worse than just JIT cache bonking out.
I've been seeing frequent and dramatic UI stutters in Safari on the iPad. Scrolling dropping from 120fps to <10 – it's bad. I'll give this a try, thank you.
Try that, it
might help, if your problems are related. Or perhaps no, who knows ;-)
Unfrotunately I don't see any easy option of deleting just the all the caches in mobile safari's developer menu, just the usual clear website data and history. Maybe it's the same (clearing the caches through developer menu on desktop safari doesn't erase history or cookies).