Just because an app uses memory and does not get smaller does not mean it is leaking. I don't know whether these would be considered leaks or not, depends on how it was allocated and whether Safari is holding it for future use once it has it, or if access is actually lost and leaked. Holding onto cached objects and updating attributes can be much faster overall than wantonly creating and assassinating objects. Makes it really hard to determine whether memory is leaking or just not returned to the OS, when you don't have access to the source and appropriate tracking tools. Even if it is not leaking, not returning it may not be the best policy.
If something is leaked than there would be a loss of data right?
In this case there is more information kept than actually needed, but why not use the ram if there is enough space on it. If there is the ram, u can better use it right?
My guess is that safari or osx keeps all surfed-to-pages in the ram as long as possible to get faster access to pages u already surfed to. If your ram is getting full, older ones get overwritten to new pages.
If safari quits, then the memory will be freed.
Probably this is the cache-memory that u can empty in safari's menubar.
Comments
I'm gonna quit and restart and see what it's like in a sec
In this case there is more information kept than actually needed, but why not use the ram if there is enough space on it. If there is the ram, u can better use it right?
My guess is that safari or osx keeps all surfed-to-pages in the ram as long as possible to get faster access to pages u already surfed to. If your ram is getting full, older ones get overwritten to new pages.
If safari quits, then the memory will be freed.
Probably this is the cache-memory that u can empty in safari's menubar.