Apple releases Faulty program in Logic 9

Question

Please note very important posts and test showing conclusive errors with certain plugins at post numbers:
55
56
71
79
(This is using Logic 9.1.1 in Snow Leopard 10.6.3)
Ok, so Logics ram usage has been mentioned many times before, mainly from people who just want to make music and didnt know why they were hitting the "out of memory" message with Logic 9.
Im not ready to let this drop with Apple and creating a 64bit version of Logic IS NOT the get out card. Currenly Logic is using ram like a poorly programmed Windows application. It has 3 major bugs (these are under 32 bit AND 64bit mode but I will concentrate on 32bit for now)
1. It uses more ram to load a single instance of a plugin than it did under Logic 8, or than Ableton live does (Anywhere between 300-400 meg of "real" and "virtual" ram for an empty Kontakt 4 instance!)
2. It uses "real memory" and "virutal memory" in equal doses, which means you dont get the "in theory" limit of 4gb with 32bit, you hit 2gb of both and run out of memory. Ive not seen another application on Mac (apart from Apples also poorly programmed ram management in Safari) which uses real and virtual memory in equal doses as if its working like a Raid 1 arrary!
3. The biggest problem of all, it hordes ram and then DOESN'T RELEASE IT. (I might add Safari ALSO does this)
Number 3 is the biggest problem of all, which it never used to do to this degree in Logic 8. A lot of people have experienced the "lack of memory" error, closed Logic and reopened it only to find they had plenty of memory when they refreshed, here is a screen show to prove this massive bug.
[IMG]coming soon[/IMG]
In the above example I was testing simply Trilian and Omnisphere with their external server started. Logic was still chewing up ram for each patch I opened despite the data being put into the external server (not the same of course, the external server helped, but Logic was still adding between 10mb and 30mb each to real and virtual ram upon cycling patches). I might also add that the external servers (including Kontakt 4's) load exactly how big the patch is (for instance 1gb will take 1gb of ram) if you use Logic internally to do this It will use more like 1.5gb for a 1gb patch...
Anyway in the above example I loaded a hand full of patches in both Omnisphere and Trilian and put in one instance of AmpliTube 3 and a Logic channel EQ...already nearly 2gb of ram used!! I removed all the plugins and still this ram is used.
It should now read 200meg real and 100gb virutal (which is what Logic uses when you first load it with an empty song) - when I quit logic keeping an eye on the activity monitor you'll see the 300meg it should actually be using disappear first and the remaining gb's its hoarding pause for a minute before being properly flushed out of the memory. Very strange but ive noticed Safari does something very similar so whatever Apple are doing its messing up ram usage in both.
This week im going to run extensive tests, take screenshots and videos on how it handles ram compared to Logic 8 and Ableton Live. All I can do is try to submit them to Apple (somehow?) in the hope they'll fix this problem.
Now before you say it, at the minute NO 64bit Logic is NOT the answer.
Why? Because I have hundreds of plugins and only 4 of them are 64bit! in the mean time I CANNOT work only being able to see one 32bit plugin at a time, and have it disappear if I touch the track mixer with my mouse. There are time when I NEED to see 3 plugins at a time working together. I also dont like the floating window and I have a number of plugs where the GUI doesn't even load in the 32bit bridge.
I think its going to take about a year for all these plugins to be updated and some of my favourites will never be updated (the free plugins such as DFX and MDA which I use for creative purposes)
But the bigger problem here is that I never ever had problems with memory usage on huge 100+ track projects on my 8 year old G5 which only had 3gb of ram in Logic 7. Now I have a 16gb of ram and a brand new i7 processor It seems I can barely do anything with out worrying about memory usage!
Another reason 64bit is NOT the answer is because Logic continues to hoard, bloat and not release ram in 64bit mode. Generally users do not have more than 8gb of ram on their system at the minute (infact very few have splurged on the 16gb I have as it costs nearly as much as the entire computer and you get no benefit unless heavily multitasking, which in audio we're not...or everything is 64bit (or everyone release external servers for their sample management)) just because an application CAN make use of 16gb of ram doesn't mean it should...and if Logic continues to chew ram like this its going to eat into ram at an incredible rate (which it already is) and suddenly its 64bit mode when you have 8gb of ram in your system is only going to be as efficient as 32bit Logic 7 was with 3gb of ram!
Apple needs to do something about this poor ram management, opening and closing a song continually while you are writing or mixing is not helping the work flow at all. These are three HUGE bugs built into Logic and im very surprised a bigger fuss has not been made of these im also disappointed. I probably wouldn't have noticed them had I not been waiting for two months for all my new audio equipment to arrive and had so much time to test and play with Logic and noticed that when not even writing a song and just playing with no more than 4 tracks Id continually run into "out of memory" message. Last night I simply cycled through all my plugins to take screenshots of each (im planning on printing off an A1 poster of all my plugins to give me an easy to view visual look of what is on the system to counter the horrible list of developers names we have to cycle through!) and when I got to the end of list (keeping in mind I still had one track with no plugins on and id just been replacing the plugin with the next on the list) Logic had run out of memory!
I doubt Apple reads these forums so when ive completed my conclusive research Im going to need a way to get it sent off to Apple properly...any help there?

Answer 1

Lefire wrote:
(This is using Logic 9.1.1 in Snow Leopard 10.6.3)
I suggest you update to 9.1.2, which supposedly fixes precisely some of the things you mention, and 10.6.4.
Get back to us when you've caught your breath and let us know if it's still happening.
BTW, from my limited understanding of memory management, it is completely irrelevant whether an app frees up memory while it's still open - it might be beneficial and faster to hang on to it, depending on what you're using.
The background stuff is irrelevant and rarely subject to a layman's "common sense" - concentrate on whether the stuff you actually work with is working or not.
And for that, it's 9.1.2 and 10.6.4.