John Kitchen wrote:
mightymilk wrote:
I misunderstood your post, that's an honest mistake.
Not the first time this has happened.
You have made a few more mistakes.
- You claim that Safari consuming 1GB of RAM is not normal, and that this must be a Lion problem. I have Safari running in this Snow Leopard iMac right now and it is consuming 1.05GBs of RAM. 2 tabs open. No Lion.
- You claim to know what I'm thinking about the properness of Lion's memory handling. You don't know what I'm thinking and if I were to put it in writing, I would not be so vague as to use the term "properly".
- You claim that memory consumption can't change if the user doesn't interact with the computer. Macs have many time based events which trigger processes which consume RAM.
- You assume that just because your computer did not show sluggish performance under prior version of OS X, that there is no way it could be sluggish under Lion unless it is the result of a memory leak. I have already provided a lengthy post explaining the most common issue when moving to new Operating Systems, which you chose to dismiss for your preferred diagnosis of "memory leak" back on the 4th page of this thread
- The final mistake I will list is that while you owe R C-R an apology for delivering the insult "Do you contridict (sic) yourself on a regular basis or just today?", you have failed to provide a public apology.
All of these are mistakes. The fourth one is one that you make repeatedly.
PS "I'm not trying to insult your intelligence but..." was another mistake
1. 1GB of RAM for 1 Tab open from 1 Website is not normal. If I was playing a Flash game, or streaming 1080P video, okay. But under normal use... no.
2. That statement makes absolutely no sense, so I'm not going to even bother trying to respond to it.
3. I never said it can't consume RAM without user input. I said it shouldn't consume all RAM without a user interfacing with it... or a person accessing the computer remotely, or streaming content to another system. A virus scan running too perhaps. But an ideal system that's not running weekly scripts or anything out of the ordinary. Sorry no.
4. The sluggishness ONLY appears when all memory has been consumed, that's been clearly stated.
5. I don't need to apologize to R C-R because the man has done nothing to acknowledge that there could be a problem, instead he's gone wildly off topic by talking about the nature of OS X and using all available memory is normal under OS X. Despite the fact that most other posts have seen a massive increase in memory consumption, and many to the point of total depletion.
I'll say it again. Funny that only you and R C-R seem to think this is normal behavior for OS X. The only thing you two seem interested in doing is patting yourselves on the back, and posting long rants about how Activity Monitor and OS X handles memory. Instead of tackling the issue head on why Lion is suddenly using drastically more Memory than other releases... to the point of consuming the entire Free and Inactive sectors, even on systemes with 12+ GB of RAM, or the sluggish performance some are experiecing when they've reached that point.
Anything else you'd like to add, or are you done?