After Effects error: string memory leak ( 83 :: 2 )

Did you save your CC 2017 version?  Use it.  This new one won't be worth a hoot until the first major bug fix... or maybe the second.

Impossible to know with the actual crash log and ideally a description of your steps. In 15+ years of using AE I've never come across this error, so the conditions when it appears are very specific. Knowing what's involved might help. Perhaps you use some expressions or scripts or generally something exotic to do with text...

Mylenium

Yes I'm having the same problem.

I've gotten it once or twice but I just ignored it.  However if it's happening every time you close the app you should probably go back to 2017 for the time being and either contact support or submit a bug report.

Yep, I see the same error window when closing out.

I have the same Mac setup but late 2013.

Macbook Pro (Retina, 15-inch, Mid 2014) 16GB RAM, NVIDIA GeForce 750M

Yep, me too. MacBook Pro 15" Touch, High Sierra

I am also getting this message EVERY SINGLE TIME I CLOSE (or crash.)

MacPro (late 2013), El Capitan, 64 gb RAM, AMD FirePro D700

Same here !

Same issue, first time tonight though since updating 3 days ago? Is this a good thing????

Same here. Never had that with previous Ae versions.

I'm having the same issue -- usually happens after leaving it open for a while.  Replying to see if there's a solution.

Same error here on Windows 10 professional. AE was only open for an hour or so after a restart.

Every time I use AE outside on my patio I get screamed at by this one Blue Jay.   Can anyone tell me why this is?  I know it's After Effects fault because that's the only time I ever use my laptop on the patio.  Should I file a bird report?

Oh yah...the laptop is a Dell, if that helps.

Yes, I just had the same problem for the 1st time after updated to CC2018.

yea this happens to me too when i exit the app without first purging all memory and cache.

i have the same problem with the memory leak and i thought 32Gig DDR3 RAM will be more than sufficient, then i get windows error in memory leak for after effects. no problems when app is idle. my simplest resolution is:

1.) to not keep any profile open when not in use as the app will drain the memory.

2.) occasionally purge all memory and cache when profile is open.

3.) purge all memory and cache before you close the app.

i was like wtf when i saw the memory go up 254mb (reasonable), 9k (uh oh), 21k (what the hell)

you can add all the memory you want, it will probably feed after effects more.

hope this helps.

I've noticed this too with 2018.

When previewing a project it seems to be re-writing over the RAM instead of caching and playing that back.

Sometimes cant get a smooth playback of what should be an already rendered section.

I anyone has a reproductible case on her/his machine, could you generate a log (Help menu), and send it over here? This may shed some new light.

I tried putting 20/32GB RAM on reserve for other apps, which is a lot being that AE is the only active app, still encounter memory leaks. seems like the problem may be in the memory caching or if it even caches at all. if I don't manually empty all cache, it goes viral in about an hour with 12GB RAM for AE so that it will eat the reserve RAM slowly. for me I can get by, just adds a higher level of maintenance than having to get the Windows error for no RAM left for it then pc reboots.

Feel like this is a hard thing to log and replicate considering most times it just happens when you close the application after having it open for a while, but I get it a fair bit.

Have even had my computer BSOD straight after getting the windows memory full error. Also did a 4 Hour+ render one time and I had a layer get "stuck" towards the end, though this may have been a cache/memory error (had to re-render the end bit after restarting AE and purging).

So yeahhh 2018 a lil' broken atm with these memory issues lol, might head back to 2017 considering there hasn't been much changed (that I use) and text previewing is also broken af which is another topic but a HUGE dealbreaker for me.

Incept2ed  wrote

 

I get it a fair bit.

 

Have even had my computer BSOD straight after

 

might head back to 2017

I nearly couldn't hold back laughter when i read you "might" head back 2017.   I almost spit coffee all over my monitors.

You're "thinking" about going to 2017, huh?    LOL

I'd love to hear your list of "pros" & "cons" that you're considering to help you make up your mind.

Gutterfish  wrote

I'd love to hear your list of "pros" & "cons" that you're considering to help you make up your mind.

 

Pros: Literally everything

Cons: ummmm... I gotta download it uhhh yeahhh

In all seriousness tho I get why you would laugh, I kinda laughed at myself after I wrote it, it was kinda a confirmation thing reading all this and writing it down.

after effects cc 2018 start up problem:

How do I disable it?  don't show new composition at start up,just quite open the program like 2017,

because I hate it asking every time!

Same thing is happening to me every time I close After Effects.  I have no problem with the program itself just get this error message. 

Imac (retina 5K, 27 inch, late 2015)

OSx - 10.11.5

Processor 3.2 GHz Intel Core i5

Memory 24GB 1600 MHz DDR3

Graphics AMD Radeon R9 M390 2048 MB

Still crashing on Quit Shamer? Can you please file a bug report here?

Thanks,

Kevin

> I have no problem with the program itself just get this error message.

This message emanates from a sub-component of AE (CORp_BIBError), and is probably the mark of a glitch in one of the AE plugins, but it is otherwise harmless when quitting, and I wish there was a way to turn it off, but did not find any.

Yes. Agreed  I get it occasionally. In fact It's happened to me twice this week and I don't know what triggers it exactly but it's harmless.

It's like when I occasionally get that "stuff not in the right bag" error, I just ignore it.

Yes I get same error message

But, it doesn't seem to affect any saved projects or working.

So why don't Adobe replace this warning box with another weird piece of artwork from Behance or better still wait a minute and show the start screen again... that should speed things up!

https://forums.adobe.com/people/sequence+W4  wrote

So why don't Adobe replace this warning box with another weird piece of artwork from Behance or better still wait a minute and show the start screen again... that should speed things up!

That's funny.   That's like asking the mayor of a beach-side community that's slowly sliding into the sea why they don't repaint the yellow lines on main street a little further apart so the line up with the wheel base of most modern sedans.

But if recent history is any indicator they've probably already got half the team working on your suggestion.  The character panel will have to wait!!!!

Gutterfish back at it again with the sassy replies

Incept2ed  wrote

 

Gutterfish back at it again with the sassy replies

You DO realize you're speaking with a man who once slept with Bridget Bardot?  Soo........

Never had it before today, and then twice. It did not happen when closing the app, it did while trying to move add a comp from the Projects list. The app just freezes.

I don't know if it makes any difference, but before it started doing this, I had an issue when importing another AE file as I wanted one of the comps there. There was some duplicate script and I kept getting variable errors even after I deleted the doubled version. Anyway, I restarted AE and the script errors were gone. Straight after I started having this memory leak error.

Same problem here. I get the message when I quit the program, every time. Other than the error message window, it doesn't seem to be hurting anything.

But would love a fix for this, Adobe.

have the same problem since 2 days

I was getting the same error almost every time I closed AE (on Windows 7).

So I did some testing on my own and found that it appears to be caused by a lag in the "sync" operation. So I went into Preferences > Sync Settings and disabled the items checked (which basically sync up the presets and shortcuts to my other machine).

Ever since I disabled the sync settings, the error has not appeared.

So it looks like Adobe needs to do some further refinement on the sync operations. I'm using an Enterprise version of Creative Cloud if that makes any difference. I log in using a Federated ID (which is always on since it requires TypeKit to function).

Hope this helps!

Eric

I think you may be right Eric.  I don't usually have the CC app running but I had it running for the past couple of days and got the error several times, also got the "stuff not in the right bag" error a couple of times.  Killed the CC app and have not had the error since.

Could be a coincidence or it could be the source of the problem.

je n'ai pas l impression d'un crash. plutot d'un avertissement , mais cela le fait aussi sur mon système  mac  book pro 2014.. 

I've had this error twice now when exiting AFX.  After the first error, I saw this forum thread and disabled sync settings in AFX (as Eric suggested).  Didn't see the error again until today.

I don't leave the CC app open (but turned off sync settings there also)

hmmm...

Description is simple. Saved and closed out of After Effects generates the error.

Definitely file a bug, Shamer.

Thanks,
Kevin