1. Welcome to the new MacRumors forums. See our announcement and read our FAQ

SafariForWebkitDevelopment Web Content over 2GB

Discussion in 'OS X Mountain Lion (10.8)' started by Michael Goff, May 17, 2013.

  1. macrumors 601

    Michael Goff

    Is there some way to lower the amount of RAM that's used? I like the speed and all, but it isn't exactly friendly with resources.
  2. macrumors 603


    No current way atm.
  3. macrumors 601

    Michael Goff


    Next question is why it's like that. I don't get it.
  4. macrumors demi-god


    I believe the idea is to use memory if available to cache pages for faster access. As long as the system still has memory available, this is not a problem.
  5. benwiggy, May 18, 2013
    Last edited: May 18, 2013

    macrumors 68020

    Free RAM is wasted RAM. RAM is there to be used. OS X will use as much RAM as possible. That's a Good Thing™.

    You don't need to worry about freeing up precious RAM in order to anticipate launching more apps in the future. OS X is well aware that you might do this, and is prepared for it.

    If you're running "SafariForWebkitDevelopment" in 10.8.4, then you're a developer running a test environment, so that software is probably not optimized for efficient use of resources.
  6. macrumors 601

    Michael Goff

    So ... the high use of RAM is -why- it's so fast? Not complaining, just making sure I'm understanding you right.

    So you think it will be more optimized as time goes on?

    Also, I guess I'm still not completely out of the mindset of "watch my RAM". XD I'm going to change this, eventually.
  7. macrumors demi-god


    The idea is the cache saves pages you visited in memory, so if you go back to that page it will load faster since the page is cached locally and almost nothing needs to be redownloaded from the Internet.

    You can see it yourself if you clear the cache then visit a page twice. The second time will be faster due to the cache.
  8. macrumors 68020

    Ok but then why does safari reload tabs or pages when you swipe to go back, shouldnt those be in the cache ready for viewing, a la Chrome? I'm not trying to argue against your point. In theory it sounds good.
  9. macrumors demi-god


    Just from tinkering around a bit using both, it looks to me like they are both using the cache, but Safari renders the page again where Chrome does not. Why that is, I have no idea. :confused:

Share This Page