but i'm not some OS X guru, so i could have it wrong. i'd be happy to email that screenshot to anyone to post here.Īnyway, it sure looks to me like logic uses more than 2 GB of RAM on my system.
MAC CORE AUDIO BUG INSTALL
I have to install a new hard drive, but if you want after that i can load up another song and grab a screenshot of these three windows (TOP, activity monitor, and process viewer) showing the RAM reporting for logic. The onlly programs open were logic, activity monitor, TOP, and process viewer. the system memory reported in Activity Monitor claimed 3.84 GB used, 164.97 MB free. The system memory reported in TOP claimed 3.84 G used, 165M free. This virtual memory numbers for logic in the three windows was 3.50 GB, 3.50 GB, and 3,667,212 kbytes respectively. The resident memory size reported for logic in the process viewer/stats window was 3,322,580 kbytes. The RPRVT figure reported by TOP for logic was 3.12 G. The "real memory" figure reported for logic by the activity monitor was 3.17 GB. I just turned EXS virtual memory off and loaded up 9 performance set/legato instruments.
![mac core audio bug mac core audio bug](https://i.stack.imgur.com/VQy8y.png)
Well, i'm not sure what i can say other than what i see on my system. If your disk is having a problem, this should tell you. Just don't go crazy with it as it creates a file (count x bs) big! The results will tell you, among other things, the speed of the transfer. You can vary the block size (bs) and count. Time dd if=/dev/zero of=/Volumes/volumename/test bs=1024 count=10000 Time dd if=/dev/zero of=/Users/yourname/Desktop/test bs=1024 count=10000
![mac core audio bug mac core audio bug](https://venturebeat.com/wp-content/uploads/2019/05/playstation-vr-foveating-rendering.png)
If you suspect disk performance problems, you can use 'iostat -w 5' which will poll your system every 5 seconds and give you summaries of disk transactions and MB transfer counts.Ī neat, built-in way to test your disk performance is the following (in the Terminal): In other words, Panther *may* help you here, but I couldn't guarantee it. I am unsure as to whether Logic takes advantage of that in the more recent releases. Someone here can correct me if I am wrong, but I believe Panther raises the ceiling on the active RAM size of any single application instance from 2GB to 4GB.
![mac core audio bug mac core audio bug](https://i.stack.imgur.com/JI68K.png)
If you attempt to play and those numbers change, you are hitting virtual memory, and are bound to choke the data flowand kill Core Audio. Is it close to 2GB? Also, if you are using 'top' in the Terminal, look at the number of pageins and pageouts. First, after the song is loaded, watch the size of the Logic instance. If you aren't saturating your CPUs, you can rule that out. You can use the Jaguar Activity monitor or 'top' in the terminal. Make sure you are set in Energy Saver to Highest performance. You have to see if you are running into CPU problems or, it feels to me more likely, RAM issues. Panther has a much improved Activity Monitor. My advice is to find out what to target when seeking a cause.