Previous 1 2 3 4 5 Next 72 Replies Latest reply: Dec 19, 2013 7:39 PM by johnfromplantation Go to original post
  • rahul.l Level 1 (0 points)

    Are you suggesting that updating to 10.6.8 fixes the bugs in safari? I've been using 10.6.8 for some time now and Safari still eats up too much RAM.


    There are some other bugs in 5.1 which haven't been resolved as well --

  • LexSchellings Level 6 (8,717 points)

    I was not talking to you at all. You just mingled in in this thread. I answered the Walrus.

  • rahul.l Level 1 (0 points)

    LexSchellings wrote:


    I was not talking to you at all. You just mingled in in this thread. I answered the Walrus.


    How does it matter whom you were talking to? This is an open thread and every one here is facing identical issues with Safari 5.1. Since your post ("update your OS to 10.6.8 using the combo update.") seemed to talk about some kind of a solution, asking you to elaborate is justified.


    Lastly, I didn't mingle in this thread. If you read through previous posts you'll notice I've been on it for a few weeks.

  • David Kinnear2 Level 1 (15 points)

    Actually, I have had this problem while running OS X 10.7.1.  I have had no issues with Chrome.

  • LexSchellings Level 6 (8,717 points)

    Yes rahu, you did not read who I was answering to, it was Walrus, and the Walrus does NOT have 10.6.8 !! So we were here trying to help the Walrus solve his problem, and you just mingled in telling you have a problem too. How do you know it is the same? In the supermarket you are also pushing forward in the line to be helped before the one who is at the cashier, I suppose.

  • andyBall_uk Level 7 (20,490 points)

    >>the Walrus does NOT have 10.6.8


    doesn't Safari 5.1 require 10.6.8 ?

  • LexSchellings Level 6 (8,717 points)

    look at his profile.

    I would like that he installs the latest 10.6.8 Combo Update, that often makes issues dissappear, even if you have the 10.6.8...

  • Saxman Level 2 (175 points)

    Installing the 10.6.8 Combo Update will "correct" the problem, as it includes the previous Safari, 5.0.5, which is not nearly as buggy or memory hogging as 5.1 is. I gave up awaiting Apple to release a fix for 5.1, so I did the combo update, and Safari now uses far less memory, & the Autofill is once again useful, and not a pain to use, as it is in 5.1 (where it acts like a Windows program might)....


    I sure hope Apple will refine, fix, & either  go back to the old Autofill, or make the new one an improvement, not a digression.

  • rahul.l Level 1 (0 points)

    Lex, I suspect you have trouble understanding the English language because you are making no sense buddy!


    If you read what Saxman says - 10.6.8 combo doesn't "solve" the problem with Safari 5.1 it gets rid of Safari 5.1 entirely by reverting to 5.0.5 (which I plan to do myself because switching to firefox doesn't give me access to my bookmarks, preferences, etc.).


    Software updates don't solve the RAM issues in Safari 5.1. Users on 10.7.x (Lion) are also reporting the same issue (yes, it is the same issue - I know it is the same issue because every single user mentions identical symptoms). Perhaps, you'll now suggest that users on 10.7 also try installing the 10.6.8 combo update.


    As for my supermarket etiquette - no, I don't break the line but if I ever find myself behind you in any line i'm cutting in ahead of you just for kicks!


    Please let this be the end of our silly argument, the problems with Safari are bad enough as it is.

  • andyBall_uk Level 7 (20,490 points)

    >>look at his profile


    they're so often inaccurate - and the 5.1 installer checks for OS version.


    >> that often makes issues dissappear, even if you have the 10.6.8...

    Oh I see


    @Saxman: I've seen a few reports where 10.68 combo didn't 'restore' safari 5.0.5... they may have changed the package, since certainly some said it did revert

  • 100 Watt Walrus Level 1 (0 points)

    Lex, I'm not sure where you're looking, but my profile says I'm running 10.6.8, and I am. Are you saying that you're NOT seeing this problem? That WebProcess isn't hogging over a gig of RAM under everyday use? If so, I'd be interested to know how you have it configured.


    For the record, I'm running exactly the same extension on Chrome as on Safari. Chrome has yet to grab more than 400MB of RAM, even when taxing the **** out of it (20+ tabs, editing multiple Google Wiki and Google Doc pages). Safari & WebProcess together will eat up 2GB under the same circumstances.


    Would love to know what you're doing right that everybody else in this thread is dong "wrong." (And by "wrong," I mean doing exactly the same things they alwasy did in Safari 5.0.5 and never had a problem.)

  • LexSchellings Level 6 (8,717 points)


    since you have OSX (10.6.4) 10.6.7 in your post, how to know that you in reality run 10.6.8?

    And yes, I see your problem of ram eating Webprocess, otherwise I would not try to help solve it...

    And yes, I see your problem of ram eating Safari, otherwise I would not try to help to solve it..

    And yes, I concur that Chrome is behaving "normal" in your case, and Safari not. But I am not satisfied with saying "stop using Safari, use Chrome", because that is not solving the issue, but running away from it...

    And NO, I am not doing right that you are doing wrong: I am doing nothing and have Safari behave like your Safari 5.0.5 did, like  99% of other Safari users, where Safari behaves "normal". And you are doing nothing wrong, even if you have a problem with Safari....

    Get it?

    Thank you.

    the reason why I said run the the 10.6.8 Combo is not because I want you to update, I would have suggested that too, when I knew you have 10.6.8: because it often solves these problems.. It is not about running the latest update but by running the Combo which reinstalls a lot of latest updates.

    the reason why I say, disable the Safari plugins, is because they often are at the source of these issues, if it makes the behaviour of Safari better, enable them one by one, restarting Safari after each, to see which one is the culprit, etcetera.

    These problems are not caused by a faulty app, but by something else: never forget that here in these forums are maybe 0.001 % of all users.. and nobody comes here to tell that his computer is behaving normal.


  • LexSchellings Level 6 (8,717 points)

    Walus, btw, if you want to have a copy of Safari 5.0.5 or 5.0.6 just tell me and I will give you a link to download it.

  • Saxman Level 2 (175 points)

    Lex, I know people say there's nothing wrong with Safari, that's a plug-in, or something else the user must be doing. However, I've read numerous posts of longtime Mac users who have done all they could, disabled plug-ins, reset Safari, etc, & still having problems, as I have experienced. Plus, if the problem is a few plug-ins, why doesn't Apple just figure out which ones & let everyone know, instead of thousands/millions of people having to go through the same tedious procedure, that many will find beyond their computer skll-level as well?

    That's one reason I don't buy this explanation, along with a higher level tech at Apple telling me early on they were well aware of the bugs, & assured me a fix would be very quickly forthcoming. He obviously had not gotten the word yet, or was unable to give me the party line response, for when I called back a few weeks later, as no fix had yet been issued, a different higher level tech said they'd not heard of any problems with Safari, and that I might want to disable all plug-ins & extensions!


    As to some using the combo update & not finding 5.05 in ir, I have no idea how or why that may be; if anything's changed, it had to have been done very recently, & I don't know why Apple would do that...

  • andyBall_uk Level 7 (20,490 points)

    Hi Saxman


    >>As to some using the combo update & not finding 5.05 ...


    it's in it alright, but since seemingly some have found it didn't roll back Safari & some did, Apple maybe changed the installer to check for a later version rather than automatically over-writing.