Participating Frequently

Answered

APPLICATION MEMORY FILLED ADOBE PREMIERE

Forum|Forum|6 years ago
December 22, 2019
7 replies
2202 views

SOMEONE PLEASE HELP:

While rendering a 13 minute clip that has a few minor effects to with Lumetri Color and other simple cuts, I am being forced to quit the adobe premiere pro as my application memory rises from 3.75GB to 64GB.

I have a 2019 MacBook Pro that is built for editing with 16GB of RAM and 512GB of SSD.

Yes my media cache is cleaned and yes I have tried restarting the app and the Mac.

This is the first video I am trying ot render since updating my Mac software to Catalina 10.15.2

If anybody has any idea at all how to solve this I will greatly appreciate it.

This topic has been closed for replies.

Correct answer R Neil Haugen

If you can narrow down to the section that won't export ... fairly precisely ... that would of course be good. You know you can export from X point on ... so set an in/out and export the next 30 seconds or so in front of that. Move forward through the sequence until you hit the bit that freaks.

Then move a bit farther forward, do another 30 second section, until you find one that exports.

Then you know that something in that one exact area is the issue. If you can report back here, maybe we can help get you through this.

Of course ... you should also dump all Premiere's cache and media-cache database files with Premiere closed, as those can be where the corrupt bit is stored if it's an interanal meta issue by Premiere.

Neil

M

Matěj37060577r7xb

Participant

Hello I have now the same problem. I reinstall the app and put the MacBook to factory settings and it didnt Help

R Neil Haugen

Legend

Glad you got it sorted!

Neil

Everyone's mileage always varies ...

R Neil HaugenCorrect answer

Legend

If you can narrow down to the section that won't export ... fairly precisely ... that would of course be good. You know you can export from X point on ... so set an in/out and export the next 30 seconds or so in front of that. Move forward through the sequence until you hit the bit that freaks.

Then move a bit farther forward, do another 30 second section, until you find one that exports.

Then you know that something in that one exact area is the issue. If you can report back here, maybe we can help get you through this.

Of course ... you should also dump all Premiere's cache and media-cache database files with Premiere closed, as those can be where the corrupt bit is stored if it's an interanal meta issue by Premiere.

Neil

Everyone's mileage always varies ...

I

isaacb56632110Author

Participating Frequently

I figured it out. Like you said I went section by section and narrowed it down to the small fragment that was corrupted.

Thank you so much.

R Neil Haugen

Legend

Next step is to make a new project, use the Media Browser to navigate to and select the previous project file, and then import the sequence. Make sure the old project is closed.

See if that can export the sequence out.

Everyone's mileage always varies ...

I

isaacb56632110Author

Participating Frequently

I just made a new projected and imported the previous project file and closed the old one.

Still stuck on 42% and premiere goes wack.

I really appreciate you helping me figure this thing out. I use premiere for youtube content and can't upload right now because of this

R Neil Haugen

Legend

So you've determined that the latter part and the first part work fine, but there's a bit in there that drives Premiere off the rails.

Now find that specific part, and re-build it. There's something corrupt in the Premiere meta for that bit, or a corrupt bit of media file.

Neil

Everyone's mileage always varies ...

I

isaacb56632110Author

Participating Frequently

Yes, I have just rendered out the first part and it works as well. Something in the middle is throwing premiere for a loop. Could this potentially be an image used from google?

A

Anonymous

Wow, that's some memory trashing alright.

What happens if you try to cut a new blank project with just some bars and tone in it?

I

isaacb56632110Author

Participating Frequently

So I have made some progress....

I decided to cut the whole video in half and try and render out both halves.

The second half of the video (roughly 7 minutes) rendered out fine with a LUT applied and basic transitions such as film dissolve.

I then tried to render out the first half of the video (roughly 5 minutes) with the same effects applied and it rendered farther than it has before. All the way to 57% then Premiere blows up again haha. Memory spikes from 3GB to 64GB and I am forced to quit the application.

There are no different effects applied to the first half of the video. I am totally lost with this. I don't know whether it is a memory leak, a 3rd party plug in error, or something else? I just know that the connection between the files Premiere uses and my mac are not agreeing.

A

Anonymous

I've had VRAM leaks with Red Giant Universe, but I've never seen RAM leaks like that. I've got a couple advanced troubleshooting techniques you can try if you're interested in delving into it.

First, obviously isolate the part that is actually causing the issue.

There's a couple diagnostic menus we can check for information and to change settings that might have an impact on this.

I'd also play around in the Event Viewer and with drivers.

MyerPj

Community Expert

Perhaps it is project corruption? Seeing memory spike like that.

I'm not sure how your math works; "memory rises from 3.75GB to 64GB" and on your machine specs you say; " 2019 MacBook Pro that is built for editing with 16GB of RAM". How does it go to 64GB when you only have 16 to start with?

You could try to start a brand new project then IMPORT in the current project and see if that might work. It's a starting point anyway.

I

isaacb56632110Author

Participating Frequently

The swapping memory is what allows it to go from 3.75GB to 64GB then forces the application to crash.

I have made some progress....

I decided to cut the whole video in half and try and render out both halves.

The second half of the video (roughly 7 minutes) rendered out fine with a LUT applied and basic transitions such as film dissolve.

I then tried to render out the first half of the video (roughly 5 minutes) with the same effects applied and it rendered farther than it has before. All the way to 57% then Premiere blows up again haha. Memory spikes from 3GB to 64GB and I am forced to quit the application.

There are no different effects applied to the first half of the video. I am totally lost with this. I don't know whether it is a memory leak, a 3rd party plug in error, or something else? I just know that the connection between the files Premiere uses and my mac are not agreeing.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded