49_FiveWindow

Q: Safari keeps crashing/freezing after install of El Capitan

After the install of El Capitan, Safari 9.0 keeps locking up and or crashing.

I have a Mac Book Pro 15'' 2.3 GHz i7, 4GB Memory, 500 GB HD, iOS 10.11

 

When using Safari, I will have class work up and YouTube or iTunes playing. Before El Capitan it would do those processes with out a problem. Now it seems to lock up, unable to refresh, unable to exit Safari. I have to force quit and shutdown to try and get control back. Occasionally even after the shut down it will still lock up.

MacBook Pro (15-inch Mid 2012), OS X El Capitan (10.11)

Posted on Oct 14, 2015 10:06 AM

Close

Q: Safari keeps crashing/freezing after install of El Capitan

  • All replies
  • Helpful answers

first Previous Page 30 of 38 last Next
  • by porub,

    porub porub May 12, 2016 8:15 AM in response to Luis Sequeira1
    Level 1 (16 points)
    Mac OS X
    May 12, 2016 8:15 AM in response to Luis Sequeira1

    Thank you. I updated to 10.11.5, excited to see what happens. The problem is it's hard to reproduce the "bug", clicking back and forth in YouTube just won't trigger it. It happens randomly in my system, so I wait and see.

  • by neolukas,

    neolukas neolukas May 12, 2016 11:11 AM in response to palegreenghosts
    Level 1 (4 points)
    Mac App Store
    May 12, 2016 11:11 AM in response to palegreenghosts

    What a useless post you wrote. We all know that third party can cause this but we cant figure out which one. For me Yosemite - no problem, El Cap - problem. El cap seems to be heavier on Safari and Safari is not what it used to be before the update.

     

    PS

     

    It froze on 10.11.5 as well. I have i7 macbook pro late 2013.

    The best thing to do is to go back to Yosemite or often clean history, cache and website data.

     

    Also guys I noticed the last 2 times the freezing happened, I had very very slow internet speed and Safari was struggling to load some websites and then it froze when I wanted to close tabs. Now I don't know if it has something to do with it but both times that was the case. Can you relate?

  • by palegreenghosts,

    palegreenghosts palegreenghosts May 12, 2016 1:31 PM in response to neolukas
    Level 1 (8 points)
    May 12, 2016 1:31 PM in response to neolukas

    @neolukas

     

    Apologies if you think so. Please be more descriptive of the problem you had with what I wrote and I can try and write something more useful.

     

    To answer your question: No, I can't relate.

  • by neolukas,

    neolukas neolukas May 12, 2016 1:35 PM in response to palegreenghosts
    Level 1 (4 points)
    Mac App Store
    May 12, 2016 1:35 PM in response to palegreenghosts

    Question was not for you obviously. And go and read previous 29 pages before posting. If you did it, go do it again. Everything is already said.

  • by palegreenghosts,

    palegreenghosts palegreenghosts May 12, 2016 2:09 PM in response to neolukas
    Level 1 (8 points)
    May 12, 2016 2:09 PM in response to neolukas

    @neolukas

     

    Porub, from my understanding, introduced themselves to nobody in particular, replying to the very first comment of the thread and opening with "I have pretty much the same problem."

     

    You have alluded to being familiar with the entire thread so you will know that comments are regularly posted stating they have the same problem when a discussion progresses to reveal they don't. They only had a freeze in common. Sometimes not even in Safari. Perhaps my English was bad but I was attempting to clarify what freeze Porub was having to help point them in the right direction. I believed this was part of the ethos of this discussion board as Apple don't get involved. Again, as you are very familiar with the thread you likely will have felt frustration several months ago when the discussion on one freeze that was progressing was interrupted by different freezes being mistaken for the one in the discussion and the topic was derailed. Likely, over time you understood this as human nature and instead, even though you saw a commenters freeze wasn't the same as your own, you tried to help by clarifying what freeze they might have or suggesting they be aware that several different freezes were being discussed if it looked like they didn't know this. Sometimes this can be done mistakenly but it's an attempt to save them losing time from misunderstanding prior recommendations that may not apply.

     

    As Porub replied to the first comment and didn't target a more recent one, perhaps I missed an obvious one preceding them that it followed on from, where they discussed a freeze relating to the mouse not moving and occurring when a youtube tab was open though reading an article on a different page. In reverse chronological order the comments before theirs were:

     

    • Asking why a commenter took the time to look for help when it didn't relate
    • An issue with video software freezing an iMac
    • A thanks for advice
    • A suggestion to use an extension that disables Flash and HTML5 videos from rendering in Safari
    • A message clarifying that third party extensions weren't the cause of their problem as they'd tried a clean install of their system
    • A message confirming a third party extension was causing their freeze (Flash)
    • A description of an Apple Genius replacing a Logic Board
    • A suggestion that 'this' issue (replying to the first comment) might be caused by third party products and a suggestion to identify patterns
    • A confirmation that a particular freeze was experienced in 10.11.5 beta and some steps that had been taken to try and diagnose or prevent
    • A user trying to find patterns with another users freeze to see if they share the same one

     

    Forgive any misunderstanding of English, and perhaps I need to go back more than 10 messages for it to still be obvious that a reply that didn't explicitly target other comment was obviously not intended for me to reply to, rendering my comment useless.

  • by porub,

    porub porub May 13, 2016 4:21 AM in response to 49_FiveWindow
    Level 1 (16 points)
    Mac OS X
    May 13, 2016 4:21 AM in response to 49_FiveWindow
  • by Ottius,

    Ottius Ottius May 13, 2016 4:24 AM in response to porub
    Level 1 (4 points)
    Mac OS X
    May 13, 2016 4:24 AM in response to porub

    That issue is different than what this thread is about.

  • by porub,

    porub porub May 13, 2016 4:32 AM in response to Ottius
    Level 1 (16 points)
    Mac OS X
    May 13, 2016 4:32 AM in response to Ottius

    Not really. Through these 30 pages of discussion, people shared their experiences with Safari and El Capitan freezes, lock ups.

  • by Ottius,

    Ottius Ottius May 13, 2016 4:36 AM in response to porub
    Level 1 (4 points)
    Mac OS X
    May 13, 2016 4:36 AM in response to porub

    If you read the title, this thread is about freezes caused by Safari (since 10.11). The article you posted link to is exclusive to 10.11.4 update and not exclusive to Safari. If some people post about different issues in this thread just because they can't read, it doesn't mean those two issues become the same.

  • by porub,

    porub porub May 13, 2016 4:40 AM in response to Ottius
    Level 1 (16 points)
    Mac OS X
    May 13, 2016 4:40 AM in response to Ottius

    No, they might not be the same issue, but have many things in common, if you consider the new freezes happen mostly in Safari and YouTube, what the original post was about. But I'm sorry that this link offended you so much, Mister.

  • by Ottius,

    Ottius Ottius May 13, 2016 4:45 AM in response to porub
    Level 1 (4 points)
    Mac OS X
    May 13, 2016 4:45 AM in response to porub

    It didn't offend me, mister. It just creates confusion and makes pin pointing the cause that much harder.

  • by Bob Bujic,

    Bob Bujic Bob Bujic May 13, 2016 5:51 AM in response to Ottius
    Level 1 (129 points)
    May 13, 2016 5:51 AM in response to Ottius

    Here is what I found on the Forum that helped me. I had no Safari freeze ups, but it's responsivness was way down. Opening from a bookmark would take a long time. Sometimes (but not always) it would open a page only when I repeatedly highlighted the subject line and hit Return again and again.

     

    This article helped: http://thenextweb.com/lifehacks/2010/12/04/how-when-why-to-reset-the-pram-smc-on -your-mac/#gref

     

    I did not have to use PRAM reset as suggested and I only followed SMC reset on my MBP 2009 with only 4GB of RAM. This was three days ago and my Safari is way up responding and opening various web pages without a hitch. No more hanging on the subject line. To add, Skype does not turn fans on anymore even after long conversations as it used to do. Not to mention previous problems with 3-4 open apps simultaneously. that I blamed inadequate RAM. They are now all gone.

  • by palegreenghosts,

    palegreenghosts palegreenghosts May 17, 2016 6:35 AM in response to palegreenghosts
    Level 1 (8 points)
    May 17, 2016 6:35 AM in response to palegreenghosts

    10.11.5 general update is out now. I haven't tested it myself but have read nothing to believe it will address the Safari HTML5 video tab closing/switching GUI freeze for those affected.

  • by porub,

    porub porub May 17, 2016 6:41 AM in response to palegreenghosts
    Level 1 (16 points)
    Mac OS X
    May 17, 2016 6:41 AM in response to palegreenghosts

    I've been using OSX 10.11.5 beta for almost a week now, updated to the new version yesterday, and I'm very glad to say that I haven't encountered a single freeze since switching to .5. I hope it stays that way.

  • by FatFrumos,

    FatFrumos FatFrumos May 19, 2016 2:33 PM in response to 49_FiveWindow
    Level 1 (18 points)
    Mac OS X
    May 19, 2016 2:33 PM in response to 49_FiveWindow

    I think 10.11.5 fix this. I installed it on May 8. Since then no freezes

first Previous Page 30 of 38 last Next