Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Safari is a RAM hogger on 2010 MBP 13"
- Thread starter ohla313
- Start date
- Sort by reaction score
Safari is a RAM hog. Also keep in mind that flash is also a hog with everything on Mac.
As with everyone else on this thread, I suggest Chrome. The only problem with Chrome is that it uses the AMD chip to accelerate some minor video features within the browser, which kills the battery life (or at least, this used to be a problem). I believe there's an application that controls what GPU to use, and I suggest using that to control chrome.
As with everyone else on this thread, I suggest Chrome. The only problem with Chrome is that it uses the AMD chip to accelerate some minor video features within the browser, which kills the battery life (or at least, this used to be a problem). I believe there's an application that controls what GPU to use, and I suggest using that to control chrome.
Ugh, this topics are rather silly because it shows people don't really understand memory management.
Having a bunch of free RAM is bad because it means it's not being used. A program is only a "RAM hog" if it's holding onto a bunch of RAM and isn't doing anything with it. The last part is important, because web browsers will cache previously loaded data so in order to make your web browser seem to run faster. Remember you may load hundreds of web pages which are stored in cache so Safari doesn't download those images each and every time.
The problem isn't programs using a lot of RAM, but not freeing it up for other program to use when it's closed (a memory leak).
Also, keep in mind that there's also "inactive" memory, which is data stored in memory from a closed program which can be quickly reused again if the program were to be re-opened.
Having a bunch of free RAM is bad because it means it's not being used. A program is only a "RAM hog" if it's holding onto a bunch of RAM and isn't doing anything with it. The last part is important, because web browsers will cache previously loaded data so in order to make your web browser seem to run faster. Remember you may load hundreds of web pages which are stored in cache so Safari doesn't download those images each and every time.
The problem isn't programs using a lot of RAM, but not freeing it up for other program to use when it's closed (a memory leak).
Also, keep in mind that there's also "inactive" memory, which is data stored in memory from a closed program which can be quickly reused again if the program were to be re-opened.
^^ What dagamer34 said.
As long as your computer runs normally and doesn't crash apps, everything is fine.
Using ClickToFlash can bring a great improvement too.
As long as your computer runs normally and doesn't crash apps, everything is fine.
Using ClickToFlash can bring a great improvement too.
While I prefer Chrome, I have to admit that most of Safari's problems could probably be tied to Flash... same for Chrome actually.
I think in the end, it comes down to preference. That, and I think we're all in agreement that Flash sucks.