I get what they were trying to do but this isn't an issue with Webkit/browsers. It's simply an iOS process (swcd) responsible for the deep-linking running out o

I get what they were trying to do but this isn't an issue with Webkit/browsers. It's simply an iOS process (swcd) responsible for the deep-linking running out of memory processing a bad huge file stored on the website.