Guys, I believe I found a workaround to fix this situation, at least it worked on my 6s.
It is based of the workaround suggested here by Rosyna Keller
From the Xcode -> Devices I choose my iPhone connected vis USB to my Mac and I enabled the Console.
From the Console logs is pretty much evident the crash loop interesting the daemon
com.apple.swcd (shared web content)
it crashes every 10 seconds because the "launchd" process tries to run it again and again.... It crashes due to out of memory issue because is visible a crash report from the JetSamEvent.
The speculation is the daemon crashes because the Database is using is too big due to the fact the Booking.com application uploaded too much data.
The problem is still visible if you uninstall the Booking.com application, because in this situation IOS automatically should remove the data added by the Booking.com app on the SWCD database, but unfortunately it doesn't because the SWCD daemon is in a crash loop!
The trick is to remove the application before the SWCD daemon starts the crash loop.
To achieve the goal I followed these steps:
1) Connect your device via USB to your PC/MAC
2) Turn on AIRPLAN mode
3) Uninstall the Booking.com application
4) Go to "Settings->Safari
5) Set "Search Engine" to Bing
6) Disable "Search Engine Suggestions"
7) Disable "Safari Suggestions"
8) Disable "Quick Website Search"
9) Disable "Block pop-ups"
10) Disable any "Content Blockers" enabled (Example AdBlock plus)
11) Disable "Fraudulent Website Warning"
12) Go in "Advanced" and disable "Javascript"
13) Stil in airplane mode, reboot your device.
14) Keep the airplane mode. Re-Install from I-Tunes the "Booking application"
15) Keep the airplane mode. Run the Booking application.
16) After you didn't allow the Booking application to send you notification and to use the GPS, kill the Booking application using the IOS task manager (double click on the home button and swipe away the app).
17) Uninstall the Booking.com application
18) Exit from the AIRPLAN mode
19) Now the problem should be fixed and you can re-enable javascript and the other settings in Safari
Hope this will help :-)
Cheers
Raffa
<Link Edited by Host>
