-
U_MemTracked object.
OK, so I’ve looked at a bunch of forums full of people talking a lot of crap about this particular error… the most common suggestions have been ‘get more RAM’ and ‘Are you using WinXP SP2? …that will do it’… I am neither using XP nor is RAM the issue.
I RAM Preview all day long with AE and NEVER have a problem. This one series of image sequences I am trying to access however presents me with the U_MemTracked Object error, all the while I am staring at my Activity Monitor which is telling me I still have many GB of RAM available. I have my Max mem usage at 120% (3GB), Maximum RAM cache at 60% (1.8GB) and have enabled disk cache with PLENTY of space allocation. The issue is not RAM… does ANYone out there have any other suggestions about why this particular set of image sequences might carry this error with them? Even in FCheck they tend to lag when being read… but are still accessible. I would put it down to file corruption for the whole sequence, but so far 2/5 animals rendered from effectively the same maya file have been fine. It all comes down to not wanting to re-render this sequence again as I KNOW that the files in the sequence are individually recognizable by both FCheck and AE.
I am running Leopard on a 2.8GHz Intel Core 2 Duo with 4GB of DDR2 SDRAM, any whizzes out there care to give this one a go?
Cheers
Ben -
1 Reply
-
Not sure if this will solve your problem but your max memory usage is WAY to high. You want it so that the % equals out to LESS THAN 1 gig.
Reply to this Discussion! Login or Sign Up