Participating Frequently

Question

Premiere Pro crashing. Force Quit window opening. Run out of application memory.

Forum|Forum|8 years ago
July 19, 2017
5 replies
3132 views

I can't export my timeline anymore. I keep getting this error message after like an hour of exporting. It keeps saying The Force Quit Applications window pops open and says "Your system has run out of memory" and that Adobe Premiere is (paused).

I'm using Lumetri and also the third part app Twixtor on some of the clips.

Also this might be another clue as to the problem:

I also had errors in my timeline. A sequence just completely stopped playing. Even if I copied and pasted it into the middle of my film (where the sequence belongs), the entire film would play but ultimately stop playing when it reached that part. I rectified this by going to each clip individually, and making a slight opacity change then back, to cause it to turn red in need of a re render. Once I rerendered, it played just fine.

I'm running a Mac Pro (late 2013) trash can, 64gb ram, 2.7 ghz 12 core, intel, xeon 5, AMD FirePro D700 6144 MB

(I realize when I opened my system settings, that my ram was listed as only 48 GB 1866 MHz DDR3. I cleaned it a month ago so I'll reinsert the ram and try to export again, don't think that would because this to be the issue do you?)

Also I was running the latest Premiere Pro 11.1.2 so I tried to reinstall 11.1.1 but that isn't working either.

This topic has been closed for replies.

A

anthonysneedAuthor

Participating Frequently

I tried a new approach,

I opened the session up on my new Macbook Pro. It loaded and played just fine. But it completely crashed on export.

I also removed all the Twixtor files to see if that was the cause. It wasn't...

I'm going to try Dean's idea today.

A

anthonysneedAuthor

Participating Frequently

Ok, so I went, reseated my ram and it now reads correctly as 64gb of ram. That problem is fixed.

I also reinstalled OSX.

I tried to export again over night and woke up to another Force Quit Ram problem:

I also realize that it's just slow exporting in general, the estimated time remaining always starts off low but slows and slows.

So before I try Dean's suggestion of deleting the problem portion in question (which isn't a problem any longer), I've decided to copy the sequence, then remove all instances of the third party plug in Twixtor to identify that it's Premiere Pro specific.

Also not sure if this matters but my timeline is 1080 and has a good mix of HD and 4k footage. The 4k stuff is scaled down, or used for zooms, repositioning, etc.

A

anthonysneedAuthor

Participating Frequently

Both of your answers make perfect sense I will try these and report back.

Thank you!

D

DeanUtian

Community Expert

Since you've identified a clip that has caused other problems in your sequence, I'd suggest deleting it, saving your project as a new file and then try export. See if it manages to complete without the file.

I've seen problems with a single file causing he whole project to fail.

A

anthonysneedAuthor

Participating Frequently

Dean actually it wasn't specific clip. It was a specific sequence. For instance, in my film there are 10 scenes. These are 10 separate sequences which I then copy and paste into the main film sequence. I noticed one was giving me trouble and wouldn't play both in the main film sequence and also it's own sequence. Then I made those changes I mentioned to force it to be in need of a rerender and now they work. Pretty annoying to be honest. But after rereading your post, it's not a single file or clip that I can identify as the culprit.

jasontcox

Inspiring

Frustrating, but glad you managed to make it work!

jasontcox

Inspiring

The fact that your System is mis-reading the amount of RAM it has installed is a pretty big red flag. There could be something corrupt with the RAM. Could be a simple fix of pull them out, blowing a bit and sticking them back in, or it could be something else. Is this third party RAM?

A

anthonysneedAuthor

Participating Frequently

No the RAM isn't third party. I bought the full 64gb when the new Mac Pro came out. Do you thing since I've reseated it, and it now says 64gb instead of 48 that it's fine now? (I don't think this is the culprit anymore since it crashed on my MacBook Pro as well.)

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