Skip to main content
Participant
June 10, 2017
Question

Premiere low on memory?

  • June 10, 2017
  • 2 replies
  • 8006 views

Intel i7-6700

16 GB Ram

64-bit Op

Nvidia 1060 3GB

Trying to open a current project, error saying low memory, playback won't work scrolling the timeline and inevitably crashes.  Any ideas?

This topic has been closed for replies.

2 replies

Rameez_Khan
Legend
August 10, 2017

Hi Obito_Uchibrah,

Were you able to resolve this issue? Did Neil's suggestion help?

Let us know if you need further assistance.

Thanks,

Rameez

R Neil Haugen
Legend
June 11, 2017

Any other apps open at the same time? Especially browsers or other photo/video apps?

Before opening PrPro, how much free memory do you have?

Neil

Everyone's mileage always varies ...
Participant
June 11, 2017

Hello, Neil.  Thank you for the reply.  I'm not sure how to effectively check on how much free memory there is, but I know that this is a recent issue rather than a reoccurring one.  I make sure to shut all applications down before I begin with Premiere.  This PC handles 4k Editing like a champ, and only recently did I start getting this issue.

What should I check on specifically?  Upon opening Premiere I am showing a 99% usage on both CPU and Memory in task manager.

premieregal
Community Expert
Community Expert
August 10, 2017

Hey Neil, thank you again.

Yeah It's always at 100 percent on a project that has more files in it/older project that has been in the works for about a month now.  I don't know if it just being an older project is having the effect or if having multiple files in it is what's doing it.  I'll say that I am editing in 4k and my computer has been doing a great job of editing it up until now.  Newer projects open up instantly without any issue.  I'm not sure if I'm having a cloud compatibility issue or what it could be.

Anyone else who knows more on this would be really awesome.  I have clients I'm shooting/editing for, so I have to have a working software.


Hi there - I would concur with Neil. Cleaning your media cache seems to always fix this issue.