Skip to main content
Known Participant
November 3, 2017
Answered

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

  • November 3, 2017
  • 55 replies
  • 97237 views

Since upgrading to the latest AE, I'm getting this error every time I close out of After Effects - basically crashing on exit.  Anyone else?

This is on a Macbook Pro (Retina, 15-inch, Mid 2014) 16GB RAM, NVIDIA GeForce 750M.  Haven't upgraded the PC workstation yet to see it is replicated on that system.

Shawn

    This topic has been closed for replies.
    Correct answer Kevin-Monahan

    Definitely file a bug, Shamer.

    Thanks,
    Kevin

    55 replies

    Participant
    September 9, 2020

    Still getting this issue.

    September 22, 2020

    same here. i don't honestly know much about this type of stuff, since i am just an instagram editor. whenever i plan on closing after effects, i purge my disk cache and stuff before i do, and ive encountered this error twice already. at first i thought that it was just a bug and that it was fine but i learned about how memory leaks can damage the application. ive also found absolutely no solution to this (i use an imac). i'm kinda worried about what this can do to after effects and my computer, since i don't want to uninstall it or download another version because that takes too much work. i just really need a solution, and quick.

    Participant
    July 28, 2020

    is it actually possible that a software manufacturer like adobe can let such a problem persist for years? it is simply incredible. I have the same problem.

    Known Participant
    July 29, 2020
    This problem was definitely not anti virus and a new update solved the
    issue for me. But Adobe doesn't care... As long as we pay they are happy
    Participant
    July 19, 2020

    you just need to turn off your antivirus 🙂 this solution it worked for me 🙂 

    turn the real-time protection off 🙂

    Participant
    December 17, 2019

    Import psd file рoses a problem.

    AAE 2020

    Participant
    December 16, 2019

    SAME PROBLEM HERE, NEVER HAPPENED BEFORE GETTING 2020

    Inspiring
    November 26, 2019

    Same on Windows 10 1809, Alienware 17R3, Intel Core i7 6820HK, 32GB RAM, nVidia GeForce 980M.

    Participant
    November 28, 2019

    Same on windows 10 1909, msi p75 creator, i9 9880H, RTX 2070 max-q, 32GB RAM.

    Inspiring
    November 24, 2019

    Yep, same here!

    Participating Frequently
    November 19, 2019

    Happens to me on close as well, but only when I first try exporting to Media Encoder, which never appears in the render queue. 

    Known Participant
    November 16, 2019

    SAme issue on Windows 10.... And getting it at times with Photoshop too. Only since the latest update! So sick and tired of Adobe holding us ransom!

    stefang58242413
    Participating Frequently
    November 18, 2019

    Same here (Windows) since I update AE to the latest version 😞

     

    Participant
    September 30, 2019

    Same !!!

    Participant
    October 4, 2019

    I'm not going to lie, I didn't read this whole thread to see if anyone else has this answer, so apologies if I'm repeating anyone, but I've had this same problem since switching to a trash can (Mac Pro Late 2013 - 3 GHz 8-Core Intel Xeon E5 - 64 GB 1866 MHz DDR3 - running os 10.12.6). After much swearing and frustration, we finally figured it's something between external the Blackmagic gfx card (UltraStudio Express) and After Effects. As long as I unplug that thing, I'm fine. As soon as I plug it in, I crash every time I try to close a project or quit AE. For me it's an okay workaround, because I only need to use the Blackmagic card when I have clients. All that to say, I don't know how to solve your problem on a MacBook Pro, but this is my experience and my workaround. Hopefully it helps you get a little closer to figuring out a solution! ETA: I'm on cc 2019, but this has happened since cc 2017.

    P.M.B
    Legend
    October 19, 2019

    The crash is related to the creative cloud app. synch.  Kill the CC app and you won't get the error.  

    ~Gutterfish