sorinfromtoronto wrote:
God forbid we admit there is a problem with Mavericks. The choices are:
1. You installed BAD software. You should know better.
2. You are using non Apple software. You got what you asked for.
3. You are using only Apple software. Your hardware is defective.
4. None of the above. The user must be an idiot. It is the only logical explanation.
What will it take, DREW, to acknowledge that there is a problem with the Mavericks memory management??!!
PS: In the interest of full disclosure I was, am and will be a Mac user.
Sorin Vacaru
I believe in isolating the fault to see better evidence before stating something is faulty.
I have been bitten by false assumptions in the past, it's very easy to assume the last major change caused a problem, when it was the result of previous changes to a system.
If there is lots of software installed it's difficult to assign blame to 10.9 alone, especially when I have seen many cases of users complaining about poor performance with 10.9 on these forums. It often disappears when the user either clean installs, or uses Etrecheck to remove & update older software. It just looks like 10.9 has so many changes that older software falls apart and affects the entire OS. It's hardly surprising when you consider some people have third party software running at a system level designed for 10.6, 10.5…
Personally I think it is mostly Apple's fault - they make upgrades/ Migration Assistant/ Time Machine restores so simple but fail to inform users about everything that is old or deprecated but still active.
I agree with your points 1-2.
3. Even Apple's older software fails on 10.9 - try using 'Save as' in Pages '08, you are seeing Aperture fail too. Ideally Apple should be updating all of their software that is running on 10.9, but I think the yearly release cycle & new pricing suggests they won't do that.
I can't see how any user could cause this 'out of memory' dialog via point 4 unless they are doing things they are not telling us.
sorinfromtoronto wrote:
What will it take, DREW, to acknowledge that there is a problem with the Mavericks memory management??!!
I don't deny there are issues with 10.9 & it's probable that certain hardware causes it to show up more often too. I just think people need to rule out the old installed stuff first, since a trip to the Apple store may end up in a clean install anyway.
The 'documentation' I was referring to earlier was simply to allow chonki3 to take a nice list of dates/ times /activities/ screenshots to show the Apple service agent. Hopefully that would help show that there is a real, recurring issue instead of simply telling an engineer to look at this topic & unpick 10 pages - that should be Apples job. Reproducing errors like this is 1/2 the battle of troubleshooting & resolving them.
FWIW I think we both agree on more than you assume or perhaps I'm just misjudging?
Disclosure: I don't work for Apple & have no control over any of this stuff, so my acknowledgement of anything here has zero value here, sorry. I have also used Macs for many years & continue to do so.