I think it may be Lion. Since Apple has come out with a new version of FCP and Motion, they probably aren’t too worried about incompatibility issues with the old version.
Motion 4 is behaving exactly as you describe, almost like it’s running out of memory. I have a fairly complex animation that I’m working on, and it’s been agony. I’m in the process of learning AE, but I chose to do this project in Motion, since I’m already comfortable with it. Now that appears to have been a mistake. Fortunately, the animation is only one minute long, and I’ve almost got it done.
I’m accelerating my switch to AE. I may eventually try the new FCP and Motion, but I think I’ll wait until Mountain Lion comes out.
Regards,
Tom