Q: Lion - Memory Usage Problems

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?

R C-R wrote:

 

mightymilk wrote:

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 ...

In several posts I have explained that while there could be a memory use problem, Activity Monitor is not an adequate tool to diagnose its cause, why that is so, & some steps to take to try to determine what is. Several users have provided info that points to something other than a flaw in any Apple-provided software.

 

You have done little besides to insist that you know how memory management works, that you can somehow tell what the cause of your performance issue is without doing anything besides looking at Activity Monitor, & backed that with some absurdly simplistic arguments. You presume all reported problems are caused by the same thing, & that there must be a problem even when no specific problem is reported other than high memory use.

 

You ignore anything that doesn't support your wild guess that some piece of Apple-provided software is at fault -- even though you are not sure which one it is. You have no explanation why the same issues don't affect everyone. You exaggerate, oversimplify, & attack anyone that doesn't agree with you, frequently by grossly misrepresenting what they say. This is clearly not the result of honest mistakes.

 

None of this helps anyone. Problems are not solved by making wild guesses that don't fit the facts. I don't care about apologies but I do care about helping people solve problems. I'm not sure what you care about but if a part of it is solving problems, you have a very odd way of going about it.

I heard all your arguments about the delay in Activity Monitors reporting and everything else you said.  You haven't provided a single ounce of help, and have made every effort to rebut any possibility that there is a serious memory issue under OS X.  You may not realize it, but you're not the only person with an in-depth understanding of Hardware and Software, and even though making 3 paragraph posts about Page Filing, Activity Monitor, and general OS design might impress people who don't know much about computers... it's extremely evident that your posts are all substance that's wildly off topic and most of the time totally irrelevant to the issue.  You won't be able to help anyone until you acknowledge that there is an issue, and from what I can tell you're still trying to hold onto this being business as usual for OS X.

If you have something of substance that will actually help users solve this issue, feel free to contribute.

Otherwise you're wasting everyones time...

Have a nice day.

iVain wrote:

 

Not that I'm aware of. I haven't done altered my iMac other than upgrading my memory. I could call Apple because I did just get lion.

iVain everything you've said is being reported by numerous users, and most likely an issue with Lion itself.  These issues just don't appear out of no where, as I'm sure you already realize.  I suggest you contact Apple Feedback immediately, as well as call Apple and let them know what's going on.

Good luck.