Q: Mac Pro 6 core, D500, 256ssd 64gb loss of memory problems
-
by Linc Davis,Aug 16, 2014 6:17 PM
Linc Davis
Aug 16, 2014 6:17 PM
in response to gaijindragonslayer
Level 10
(208,044 points)
ApplicationsIt's normal in Mavericks for almost all memory to be in use, either by applications or by the file cache. That's what you should want, since unused memory is going to waste. The relevant measure of whether memory is in short supply is what Apple calls "memory pressure."
Apple's explanation of memory pressure is here. If you want a more detailed, technical description, see here.
-
Aug 16, 2014 9:03 PMby gaijindragonslayer,FIne but why do All my Wintel boxes running Windows 7 to 8.1 Pro, be they workstations from HP 8570w or Z800, and Sweetwater, MS Surface Pro 3 not have this rapid memory loss where the whole system must be rebooted. Why does my Mac Pro early 2009' MacBook Pro Retina late 2013, my MacBook Air 11" x2 or my 13" not have this problem? This is not using memory to be a men lean machine BUT bloat ware sucking the DRAM out of my computer until I am forced to reboot because the QT project meant to play in exhibit seizes and freezes. I have to use a cheap Dell to show my videos all evening.
utter nonsense that this is acceptable. This is not personal, it is business. the computer from Apple seizes up, freezes, it's a dead computer, gone to the light fantastic...it is a dead parrot pretending to be a DELL.
-
by Linc Davis,Aug 16, 2014 9:24 PM
Linc Davis
Aug 16, 2014 9:24 PM
in response to gaijindragonslayer
Level 10
(208,044 points)
Applications
Are you interested in solving the problem, or do you just want to complain?
-
Aug 17, 2014 7:47 AMby The hatter,Memory management in Mac OS is an oxymoron
Virtual volumes, RAM disk, using free memory for cache is as old as VM itself (my first taste was in the 70's)
Adobe CC and the Late Mac Pro 2013 and those Dxxxs are another even more serious issue, as is the throttling of processor and/or GPU under load.
Other than a clean system (lean mean and no 3rd party extras running in the background is a must) and build up from there, and wait for Adobe and Apple or run Windows natively?
-
Aug 17, 2014 8:48 AMby gaijindragonslayer,I have solved one aspect my Mac Pro's memory loss is not normal according to Tech Support. I do not expect OSX to be as lean as others but rendering video on my MP can result in screen judder since the OS has to have most of its Apple preferences dumped. Clean install does not resolve issue, rapid memory leak to the point OSX gives alert that I have run out of memory is according to Apple not normal.
However, I do not have this on my two MacBook Pro Retina and MacBook Airs so it is looking like hardware....which happens.....if I'm annoyed it is how long I have been detailing this issue with Apple, following voodoo, trying to get this to work... when my nMP can barely render without shuddering and juddering, now rapid loss of RAM....sorry I annoyed you.
-
by Grant Bennet-Alder,Aug 17, 2014 11:25 AM
Grant Bennet-Alder
Aug 17, 2014 11:25 AM
in response to gaijindragonslayer
Level 9
(61,390 points)
DesktopsBy far the things that cause the most issues are "just one little thing" that Users have added. These tend to cause trouble because they are badly-crafted or because they do things in violation of Developer Guidelines.
Lots of seemingly innocent little things that users have added have been seen to cause serious problems in high-end Mac Pros. If you want trouble-free, remove all the non-Apple add-ons and just run straight, unmodified Mac OS X and Major Applications, no add-ons. Readers here could easily produce a list of more than 50 add-ons that have been seen in postings here to cause trouble. When in doubt, throw it out.
The anti-malware features built into Mac OS X work better that any so-called "anti-Virus". Most of these commercial packages are simply worthless, but some also ruin performance, ruin memory utilization, or cause kernel panics without adding any additional value.
Hardware problems do not cause memory leaks.
The Mac Pro has Error Correcting Code memory, and its memory problems do not fester undetected. But you do need to check that all the memory you installed is still listed as present, because ANY problems detected at Startup can cause failing modules to be marked "absent".
-
Aug 17, 2014 12:31 PMby gaijindragonslayer,Well I have run with nothing, nothing but OSX and it still is a mess. I have used hardware test key commands, all memory is registered, all is as it should be but it still is now working. I have had numerous calls to Apple tech support. The only add ons are Apps I need for Work.
thanks for the list but it has been done and answered through tech support. Sometimes, even Apple produces a lemon.
-
by Grant Bennet-Alder,Aug 17, 2014 3:18 PM
Grant Bennet-Alder
Aug 17, 2014 3:18 PM
in response to gaijindragonslayer
Level 9
(61,390 points)
Desktops
If you think it has non-software problems, then take it to the genius bar and let them diagnose it.
