You've thrown a lot of information into that post.
Start simple and work your way up.
Do you have crashes and performance problems with every composition, even a simple one?
If not, do you have these problems with only certain kinds of source media?
If not, do you have these problems only when using Particular?
And so on.
If you're having these problems with all media and no matter what effects or plug-ins you're using, and if this just started happening, _and_ you haven't installed any new software then I'd look into RAM going bad.
Thanks for the reply. Ya, that's what makes it a bit tricky to narrow down... it's not consistant. But, it seems to be remedied by turning off some layers, so it is either an overall stress thing (I doubt it, considering the amount of RAM and CPU power), or some effect is tripping up. Again, the odd thing is that it has no problem rendering in full res (so, everything seems to 'work')... yet it often crashes with a short RAM preview, even at 1/4 res.... so, I'm not sure what to make of all that. Even scrubbing or jumping to another frame (clicking in the timeline with mouse) often triggered the error/crash.
I suspect maybe Particular is having trouble... although it didn't have it before, and everything is fine when it does a full render.
I'm thinking that RAM is being used up (even though it's 12gigs), and for whatever reason, it's tripping over that... maybe thinking it has more than it does?
System is relatively new.
Where do the error logs get written to? I think it mentioned where in the alert, but it hasn't been giving me one of those windows for a while now... just the generic 'Contact Adobe' one.
> I suspect maybe Particular is having trouble
Does this mean that you're only having problems in compositions that use Particular?
Are you running the most recent version of Particular? See this post.
That I have yet to determine. Certainly doesn't seem to crash if I take off the effects layers, such as particles. I have to isolate each thing and see. It's just difficult, since it only crashes SOME of the time, so it's hard to get an obvious cause/effect.
As far as I know, I'm using the most current version of Particular.
Seems a few things are running odd.
AfterEffects definitely becomes very sluggish in its response to mouse clicks at points... an obvious delay after each action, as if it needs time to think of each action. Seems to be a memory thing (as it's fixed with a purge), although I'm not sure why it reaches a point where AE is struggling to keep it's own interface responsive.
Still getting occasional errors when I try and view waveforms of audio layers, although it continues on fine after the error message. The error itself is kind of vague, so of no real help.
Just did another full render test, and it does it perfectly fine every time. Something to do with the RAM preview, it seems. Seems RAM is acting up both in that sense (RAM preview) as well as the sluggishness AE sometimes gets into (seemingly after you have previewed and/or jumped around the timeline a lot, so (in both cases) a lot of frames have been stored. Still not sure why it reaches a point where it's struggling. Disk Cache is on, so it shouldn't 'run out of RAM' in that sense. Really confused... An I7 with 12 gigs of RAM shouldn't be struggling like that (...even though it's random and only occassional). I was wondering if I have something configured wrong in the memory settings.
Disk Cache is on, so it shouldn't 'run out of RAM' in that sense.
Actually that could be the problem. Something with AE cacheing frames wrongly. That would in particular apply if your Particular layers use custom particles from a pre-comp. Try to turn it off andd see, if it makes a difference.
Just happened again.. freshly loaded scene/AE. Moved the timeline marker to another spot on the timeline, and got these messages:
A crash occurred while envoking... Particular... Tint.... Levels (three separate windows)
Last logged message: <3276> <dynamic link> <5> 000000001afff4d0
It was working fine for quite a while last night, but this morning, it crashed immediately as soon as I moved the timeline.
Definitely experiences delays (between the user's actions and the program's response) when there are frames stored in a RAM preview... even if it's a very short preview (few seconds). Why would that be? I've got 12 gigs of RAM, so it seems weird that even a few seconds would make the system sluggish.
What all might cause a program like AE to be sluggish in its responses (...mouse moves fine... just the reactions to any actions have a 1-3 second delay)?
Purging All clears it up fine... but it's odd that this is happening so quickly and frequently, as if I had only a few megs of RAM.
AE is showing my 12 gigs as being there. Has to be something set wrong or some simple thing. Was working fine before.
I'm in at the end of a big project, so I can't test in detail, but will look into it deeper when things are clear. Just trying to gather some theories and knowledge of what might be happening. Any info, wisdom and/or suggestions are welcome!
I'm experiencing similar behavior now on CS5.5.
The RAM cache fills up, and I know when it gets right to 99% because I use AT Monitor, and lately when it fills up it just freezes up and beach balls. This is relatively new behavior, I've never had problems with RAM preview crashes before.
I'm on Mac OSX 10.6.8 and AE CS5.5 10.5.0.253.
Dual-Core 2.8gHz, 10GB RAM