Aw Snap?

Discussion in 'General Topics' started by J_L, Mar 4, 2015.

  1. J_L

    J_L Registered Member

    Joined:
    Nov 6, 2009
    Posts:
    8,516
  2. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    1,985
    Location:
    Canada
    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?
     

    Attached Files:

  3. jdd58

    jdd58 Registered Member

    Joined:
    Jan 30, 2008
    Posts:
    527
    Location:
    USA
    I get the "aw snap" message starting with Chrome 41. Older versions are fine.
     
  4. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    17,877
    Location:
    New England
    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?
     
  5. jdd58

    jdd58 Registered Member

    Joined:
    Jan 30, 2008
    Posts:
    527
    Location:
    USA
    The thread opens fine now.
     
  6. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    17,877
    Location:
    New England
    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.
     
  7. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    1,985
    Location:
    Canada
    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.
     
  8. J_L

    J_L Registered Member

    Joined:
    Nov 6, 2009
    Posts:
    8,516
    Fixed here as well. Can't believe it was that simple...
     
  9. Dragon1952

    Dragon1952 Registered Member

    Joined:
    Sep 16, 2012
    Posts:
    1,097
    Location:
    Hollow Earth - Telos
    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/
     
  10. J_L

    J_L Registered Member

    Joined:
    Nov 6, 2009
    Posts:
    8,516
    Looks like it's finally fixed, thanks for the info!
     
  11. Dragon1952

    Dragon1952 Registered Member

    Joined:
    Sep 16, 2012
    Posts:
    1,097
    Location:
    Hollow Earth - Telos
    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.
     
  12. Dragon1952

    Dragon1952 Registered Member

    Joined:
    Sep 16, 2012
    Posts:
    1,097
    Location:
    Hollow Earth - Telos
    I think this froze up my computer today so i had to restart it.