I'm developing a browser-based mobile app built on top of jQuery Mobile, and some recent change I made is now causing safari to consistently crash on load -- this is reliably reproducible on at least two different iphones.
Since the information available is way too vague to actually figure out what is causing the crash, my question isn't so much "what's going wrong?" as it is "how would you go about debugging a safari crash?" -- I'm already working on bisecting my changes until I strike gold, but that's not always a practical approach.
EDIT: Should've clarified that the debug console doesn't produce any useful information (there are no unexpected console messages), and that the error, whatever it may be, doesn't manifest itself on a desktop browser. Also, by crash I mean the browser completely locks up and I can't get it to a usable state except by explicitly killing it from the task manager and restarting it.
Force Quit the Safari App in iOS, Relaunch Sometimes just force quitting the app and relaunching Safari is sufficient to resolve a problem with the browser: Double click on the Home button, then swipe UP on the Safari app to close it, relaunch as usual.
Open the iPhone Settings menu. On an iPhone with an early version of iOS, access the Debug Console through Settings > Safari > Developer > Debug Console. When Safari on the iPhone detects CSS, HTML, and JavaScript errors, details of each display in the debugger.
If a iOS device is synced with iTunes (OSX) crash logs can be found at ~/Library/Logs/CrashReporter/MobileDevice/
There might be some useful info there although mostly MobileSafari crashes are caused on account of low memory. Optimization optimization optimization
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With