8
August
2006

Safari crashing 21:12 on Tuesday

Both mine and my friend’s Safari browser started to crash yesterday. The browser is now quite unstable with several crashes a day. What are the odds?

This entry was posted on Tuesday, August 8th, 2006 at 21:12 and is filed under English, Tumblelog. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Tags:

6 Responses to “Safari crashing”

    Comments:

  1. Petri Says:
    August 8th, 2006 at 21:32

    I noticed the same thing. System Optimizer X solved the problem, but mine could’ve been different from yours…

  2. Niko Says:
    August 8th, 2006 at 21:52

    I tried manually repairing permissions and running the daily/weekly/monthly scripts. Let’s see if that helps.

  3. Markku Says:
    August 9th, 2006 at 11:24

    Same here.. Mine started crashing particularly on some web2.0 sites, for example when using netvibes.com or other javascript heavy services.

    I first noticed the thing as I’m working on a RoR project with a javascripted UI, and Safari keeps crashing all the time on it. This problem at least has something to do with modifying the DOM tree on the fly, which Safari doesn’t seem to like in every situation. Firefox/IE has no problems with it and the code has been checked a thousand times… Very annoying.

  4. Pascal Says:
    August 12th, 2006 at 20:53

    I have run into crashes myself, and while I wouldn’t be surprised if it turns out to be related to modifying the DOM tree, trashing the preference file has worked wonders for me every single time.

  5. Markku Says:
    August 13th, 2006 at 22:22

    Just figured it out after a couple of days of playing around.. apparently if you launch a script from inside an element which hides the element using display=’none’, Safari’s DOM tree is somehow messed up and you cannot no longer access the hidden element’s parentNode or anything above it. The situation becomes a “memory violation”, which shouldn’t happen of course.

    This was the situation for me, there seems to be a lot of unsolved Safari bugs around which crash the browser without any warning.

  6. Niko Says:
    August 15th, 2006 at 21:41

    Mine has worked fine after doing the magic permissions thing. And I’m totally keeping my hands off DOMs and trees. ;)

Leave a Reply