Previous 1 2 3 4 5 Next 149 Replies Latest reply: Aug 4, 2012 7:51 AM by Jeremy J. Dodd Go to original post
  • Bluspacecow Level 1 Level 1

    In theory yes.


    But just because it's in a sandboxed process does not mean some errant piece of code can't cause it to crash.


    It just makes it less messy when it does crash.


    Comparatively speaking before this process design in Web Kit 2 come along crashes in the browser were way more catastrophic.  A bad bit of code in an ad could crash your browser taking with it the memory of which tabs you had open to which page.  Java rendering on a page wrong could lock up the browser.


    The point of sandboxing processes isn't to magically make things crash proof - it's to lessen the effect when it does crash.


    That's what you're seeing here - one of those sandboxed processes is crashing but it's not actually crashing the browser itself  - only the content of the tabs.

  • jakhay Level 1 Level 1

    The bottom line is that the browser is much more annoying to use than it was. I'd much preferr to have my browser crash catastrophically once a month than to deal with this annoying message every 5 minutes.


    I'm getting these messages all the time after upgrading. I looked in all the suggested places and was only able to find the realplayer plugin. I haven't tried trashing it yet - just gonna use Chrome and Firefox for a while...

  • Mac SE Level 1 Level 1

    That's what you're seeing here - one of those sandboxed processes is crashing but it's not actually crashing the browser itself  - only the content of the tabs.


    Then only one tab should 'crash', just like when one plugin crashes or when a web page crashes in Chrome.

  • Bluspacecow Level 1 Level 1

    Chrome has a different process model the Safari/Webkit2


    It's actually using a modified version of Webkit but where every page is in it's own process. Always did , right from the get go before Webkit 2 come along.


    Safari / Webkit2 has just the single process for all web page content regardless of which tab or window it's in called "Safari Web Content"

  • Jaqueh Level 1 Level 1

    guys, i think i figured it out: here's my solution.

    1) Click on the safari function on your menubar

    2) select Quit Safari

    3) Download Google Chrome

    4) wait for apple to fix 5.1

  • black6 Level 2 Level 2

    Wow, awesome..  This fix worked for me too! 

  • Scott Stevenson Level 1 Level 1

    As much as I found the idea of Chrome tempting I really enjoyed my previous experience with the last Snow Leopard version of Safari I had prior to 5.1 (I believe I had Safari 5.0.5 or 5.0.6). I decided that it meant enough to me to track down and figure out how to downgrade back to my previous browser.


    I found this website and followed its instructions for 'downgrading' (really back-upgrading imho) and have managed to get a 5.0.5 version up and running.


    Hopefully Safai 5.1 didn't mess up my system's configuration too much to allow (Snow Leopard) Safari 5.0.5 to run as smooth as it did previously.



  • Mac SE Level 1 Level 1

    Scott, I'm sorry for being forward, but I love you and I want your baby

  • Samuel S Level 1 Level 1

    This is happening to me too.


    What is particularly annoying is the fact that these 'way more catastrophic' crashes didn't happen very frequently on previous versions.


    Whereas the new freezes happen constantly. I personally get them at least 5 times a day, and the gay ball happens for up to 5min before getting the option to force refresh ALL the pages, often freezing my computer again for long stretches of time.


    The fact that nobody from Apple seems to acknowledge the problem or present a solution is frustrating. They should at least enable an easy method of reverting to previous, less buggy versions.

  • grim596 Level 1 Level 1

    Just a follow up to my post describing how to delete plugins.
    Since i did it I haven't seen the problem with Safari 5.1, I have reinstalled all of the plugins i had when i deleted them and not one crash, I even deliberately loaded up 40ish different pages to test whether it was fixed or not, and it is.

  • DMLfromBeerTown Level 1 Level 1

    Thanks, this is helpful. Inside the "Internet Plugins" folder in the library I found a foldfer named "unused." I copied all the active plugins to this, and when I restarted Safari, the problem was no more. Now I'm going to move them back one by one to see what caused the issue for me.

  • Mac SE Level 1 Level 1

    Considering I don't load any plugins (using click2plugin), I fail to see what that would accomplish.

  • Jaqueh Level 1 Level 1

    You know i think it's stupid that people are offering people to REMOVE functionality from this clearly buggy browser in order to make it functional? what kind of crap for an answer is that. that's almost as bad as my telling people to download chrome, which is made to work with plugins that are the standard in the world.

  • AndrewDoan Level 1 Level 1

    Same problem here.... please someone HELP us.... I called apple support and they wouldn't help me because I don't have Apple Care.  Very frustrating!!!.. I'll keep digging around...i'll post any helpful solution if I do find it.

  • grim596 Level 1 Level 1

    But you see, after the functionality was removed it was reinstalled as safari required it.

    I did not state that in my first post, and I apologize for not posting it until last night.

    I had an epiphany this morning about what could possibly be the cause...

    Assuming everyone here who has this problem installed lion over snow leopard?? Maybe the installer left a plugin from safari 5.0 that was not compatable with safari 5.1

Previous 1 2 3 4 5 Next