> On Mar 31, 2007, at 7:53 AM, subginge wrote: > > I'm using MacPro Dual 2.66 with 4 GB RAM and just discovered that > > in the Activity Monitor, whenever a song uses more than 2 GB, > > the Real Memory cell in the monitor jumps to 16.777.216,00 TB, > > which is strange to say the least. I suspect that might be one > > of the reasons why Logic is very unstabile in certain projects. --- In logic-users@yahoogroups.com, Dave Katz <dkatz@...> wrote: > Sounds like a simple sign extension bug in Activity Monitor; the > high order bit gets set, a signed extension to 64 bits is done, and > then its displayed as an unsigned number, or something like that. > > This has nothing at all to do with Logic. > Thank's for the reply Dave! You're probably right, but I would still like to hear from other MacPro users: does Logic behave properly whith large projects or are you getting unexpected quits from bouncing, save as..., importing audio, opening certain preferences windows etc. These quits are far from unexpected for me, and once I get these crashes, the only way to deal with it is to restart Logic without Kontakt2 or Altiverb, save and restart with these plugs back in. I used to blame it on Altiverb and had the AudioEase tech support search for the bug using my project. They found a bug alright, but it wasn't this one... I have experienced the bug without Kontakt2 installed at all so I don't think that's the culprit either. I have tried to install under a new user profile on the same machine and reinstalled everything but OSX without any luck. I have repaired permissions and run System Optimizer and Maintanance with no luck. After 2 months of searching and reading posts on similar bugs I get the feeling it is ram-related. I read on Apple's Logic discussion forum that someone with the same symptomes claimed they were only happening with projects exceeding 2 gb. I cannot say with 100% certainty that this is the case here, but I'm keeping an eye on the RAM meter. Will know more later. Any suggestions are welcome. Regsrds, Ginge