Using the latest Chrome beta, I cannot access this page without the tab crashing: https://www.wilderssecurity.com/thre...ting-systems-and-applications-in-2014.373705/ It was fine before, but occurred around 2 weeks ago. Incognito mode without any extensions made no difference. IE 11 has no problem with it. Can someone troubleshoot? Thanks.
This thread in this forum is causing "He's dead, Jim!" with both Chromium and Chrome on both my computers. Is any one else seeing this?
I don't have the problem myself, but, I did find an error in a quote box in that thread. I have edited it out. Can you refresh and retry that thread again to see if the same browser(s) still crash on that thread page?
It was really simple... This post has a link in the quote box. It was a copy of the opening paragraph from the article quoted in the first post of the thread. Unfortunately, the link in the quote was corrupt. It was not a URL at all, but a huge block of text from the article. Essentially, it was just a bad link. The "fix" was that I simply edited the link to what it was in the source article. Now, while that explains why there was an error in the HTML on that page, it raises a bigger concern. Why would some browser actually fail hard on something as simple as a corrupt link format? Shouldn't they be able to work around that and simply do what the rest of us saw in our browsers? All I saw was the large block of text when I put my mouse over that bad link. My browser or tabs didn't crash.
Thank you LWM for fixing it It is strange the tab crashed with the block of text you found. Something about Chrome that couldn't deal with it properly. I'm running the latest versions, too.
Behind the bug A bug in the most recent version of the Chrome allows miscreants to crash browser tabs simply by embedding a link with a malformed URL in the HTML of a page. The vulnerability, dubbed "AwSnap" by web developer Jason Blatt, affects Chrome version 41 on Windows, OS X, and Chrome OS, though reports vary as to whether it exists in Chrome on Ubuntu or other desktop Linux flavors.......http://www.theregister.co.uk/2015/04/07/chrome_awsnap_vuln/
Fortunately, a patch that fixes the bug has already been submitted and merged, so it should become a non-issue once the Stable channel of Chrome is updated to version 42.
