Thought it might be useful if I post this; I had a video call with Becky and Matt from mnhq the other day and learnt more about the root cause of this, I had a slow morning so could afford a little time to show them what those of us on the thread (mostly) are experiencing. I did a screen share of my phone so they could see it happening in real time; Safari crashing and locking pretty much instantly. Matt explained it well to me; I’m not massively tech savvy wrt IT and the workings of websites but not completely new to it either.
It’s essentially caused by a rogue cookie or cookies. As the various ad agencies will base what adverts they display tailored to each users viewing patterns (targeted ads I guess) then some users will have received the dodgy cookie/s and some won’t. As long as the bad cookie remains in your cache, Safari will crash- hence the advice of clearing cookies/cache to solve the problem. Chrome, if I understood him correctly has additional things that stop this cookie wreaking havoc, hence some of us (not all) being able to use chrome relatively problem free.
MNHQ don’t decide which ads are displayed- that’s decided by the third party ad supplier. There are going to be thousands and thousands of different ads across MNs user base and all it takes is one or a few badly coded ads to sneak a dodgy cookie into your cache and you will then get the Safari crashes.
So @HowardTJMoon was probably closer to the truth than I was.
Matt said therefore it’s practically impossible for them to know which cookie precisely it is that is causing it. It may not even be being delivered anymore by current ads, but the fact it’s sat in your cache is what’s causing the problem. He also said although it was useful to see this happening on my phone, it’s far easier and useful to interrogate a laptop or desktop computer that they’re physically sat next to, so that they can monitor the processes directly to find the bad cookie/s. They’ve said this will be hopefully happening next week at MNHQ.
I think he also said once the offending cookie/s had been identified then steps could be taken to mean this cookie is essentially zapped from your cache- but as they still don’t know which one it is, that can’t happen yet.
Anyway sorry that’s a bit long winded, hope I relayed that fairly accurately though. @BeckyAMumsnet feel free to correct me or add anything.