Skip to main content
G
garyblakemeister
Known Participant
October 17, 2018
Question

Memory Leak while Exporting in CC2018 and CC2019

  • October 17, 2018
  • 2 replies
  • 1256 views


I have a Mid2015 Macbook Pro running Sierra 10.12.6
16GB RAM
Running the latest version of Premiere Pro CC 2019

All of a sudden I'm getting a "Your System has run out of application memory" message from OSX while exporting in Premiere CC 2018 and Premiere CC 2019.

If I watch the activity monitor during an export the Memory usage of Premiere starts growing slowly.
Then, all of a sudden about 25% of the way through, the memory usage jumps to 12GB then 15GB then 20GB and finally OSX forces me to close Premiere prior to my export completing.


Everything has been updated.  Caches have been cleared.

I've tried everything from changing the rendering from Mercury Open CL to Software Only... to turning off Syncing...
Basically all of the older fixes I've found on the message boards don't work for my issue.
I've even tried rendering the project prior to export with the same memory leak occurring.

Any help would be greatly appreciated.

This topic has been closed for replies.

2 replies

D
depth.media
Participant
November 19, 2018

I was having this same issue and have resolved it! Not sure this is the case for everyone—but I use custom AbleCine LUT's for my Canon c100, which I manually installed in the Lumetri folder. I reinstalled them when I upgraded to Premiere Pro CC 2019, but Premiere was having trouble recognizing and loading them. SOLUTION: Select every clip you have an Input LUT applied to, select none from the Input LUT dropdown, then reselect your newly installed custom LUT from the dropdown. Super frustrating, hope that helps someone.

D
depth.media
Participant
November 6, 2018

Any help would be greatly appreciated! Getting behind on client work...

    G
    garyblakemeisterAuthor
    Known Participant
    November 6, 2018

    I haven't touched Premiere in awhile, so I'll try exporting again today to see if the problem persists.
    i did recently uninstall it completely and reinstall it, so fingers crossed.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices