Logic Pro 9 Logic says " no more ram available" -impossible !!


1) And when I load my project, witch is still at the beginning and very small, I get "Memory almost saturated ..." and 10 min later I get " logic will close cause no more ram available...)
I have 8 gig ram and believe me this project is not even challenging my older laptop with 2 gig ram.

Where does this come from ?
Logic does a few other weird behavior...since 2 days now...
Nothing new added... just starting out a new prod... bad start !!

2) Just another thing here, since I installed waves mercury, ( 2 mounts ago) I only see one fat line in the CPU meter.
Before Waves, I used to see 8 tinny lines that represent 8 hyper treading cores... u know..
Why is that ? Is it losing it's capacity of hyper treading ?

3) and finally, since 2 days one of the weird behavior is that when I move a midi region later in the same track all the notes gets shuffled up on any key...

Question # 1 is the most important please !

Questions 1) A 32 bit instance of Logic Pro can only access about 2 gig of ram before you see this. Try using 64 bit mode. open your applications folder, and find Logic Pro. Select it (DON'T double click to launch) and press command i to "get info" there is a check box for 64 bit mode. Be warned: 32 bit plug-ins have this thing called "32 bit audio unit bridge" which is a shell so you can run 32 bit plug-ins in the 64 bit version of Logic.

that will resolve the memory error.

Question 2... The Logic CPU meter still does the individual meters when you double click to open it, the new meter you see is a total CPU usage meter.

Question 3... do you have the global track "Chord track" being used? Or did you transpose the track a semitone in the inspector?
Upvote 0


reply to 1) Good thing to do ! thanks, I will check this, but it was fine few
days ago. Last week I was finishing a big pop rock mix with tones of modules and waves and it was just fine... Anyway , I will do just that...

Reply to 2) thnks

Reply 3)

Yes !! the global track had the chords showing up, !!!
but if I wanted to re-analyse my piano thack, after modification, It says " can not, this is a drum track..."
What ? there is nothing about drum on that track ! A new bug appeared...

Thanks for your help...
Upvote 0


The "drum track" message might be a result of having the "no transpose" checkbox enabled in the channel strip parameters. This protects the regions on the track from being affected (transposed) by the chord track.
Upvote 0


Thanks guys...
Was true, I was running logic in 32 bit mode. A week ago was just fine this way.
Now in 64bit my ram problem went away, but now since 2 hours the 32 bit bridge is crashing all the time ... not even able to load my projet named X
But it's fine with projet Y and all others but projet X is the one I was mixing down and it' just crashing before load up !!!
Very confused !!
thanks for your help again
Upvote 0


Here is the log for my crashes... it crashes before I get to press play !

Process: Logic Pro [487]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier: com.apple.logic.pro
Version: 9.1.3 (1697.87)
Build Info: Logic-16978700~1
Code Type: X86 (Native)
Parent Process: launchd [114]

Date/Time: 2011-02-15 21:23:56.735 -0500
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6

Interval Since Last Report: 285502 sec
Crashes Since Last Report: 18
Per-App Interval Since Last Report: 38067 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: 4DF9A80D-E11A-483F-A3D7-40420557C658

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000008
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x94b15176 __kill + 10
1 libSystem.B.dylib 0x94b15168 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x94ba789d raise + 26
3 libSystem.B.dylib 0x94bbd951 __abort + 124
4 libSystem.B.dylib 0x94bbd9cd abort_report_np + 0
5 com.apple.logic.pro 0x00408209 std::eek:stream& TraceOutContainer<CEvs>(std::eek:stream&, CEvs, char const*, int) + 3981977
6 libSystem.B.dylib 0x94b1a46b _sigtramp + 43
7 ??? 0x0000000a 0 + 10
8 ...multimedia.vpa.Philharmonik 0x74568694 adl::CDataManager::WriteSet(adl::DataSet const*, unsigned int) + 72
9 ...multimedia.vpa.Philharmonik 0x744fc6c8 0x744e9000 + 79560
10 ...kmultimedia.au.Philharmonik 0x744c20c4 AU::RestoreState(void const*) + 224
11 ...kmultimedia.au.Philharmonik 0x744c5af2 AUBase::DispatchSetProperty(unsigned long, unsigned long, unsigned long, void const*, unsigned long) + 1880
12 ...kmultimedia.au.Philharmonik 0x744c800d AUBase::ComponentEntryDispatch(ComponentParameters*, AUBase*) + 715
13 ...kmultimedia.au.Philharmonik 0x744c3553 AUEntry + 33
14 ...ple.CoreServices.CarbonCore 0x91e0c7c9 CallComponentDispatch + 29
15 ...apple.audio.units.AudioUnit 0x9271c2fc AudioUnitSetProperty + 67
16 com.apple.logic.pro 0x005b4255 std::eek:stream& TraceOutContainer<CEvs>(std::eek:stream&, CEvs, char const*, int) + 5735141
17 com.apple.logic.pro 0x005b5597 std::eek:stream& TraceOutContainer<CEvs>(std::eek:stream&, CEvs, char const*, int) + 5740071
Upvote 0


LUG Emeritus
Some plugs don't play nice in the bridge. Many plugin manufacturers have taken rather a long time to come up with 64 bit AU versions for a variety of reasons. Unfortunately this means we have to put up with some basic unfriendly bridge behaviour for awhile to come.
Upvote 0