Premiere Pro 2019 randomly using all system RAM and crashing?

i was also getting the same problem, seems to stem from multicam sequences

i couldn't scrub through and edit the sequence despite having 32 gb of ram installed.

I am also unable to export my sequence if the video got too long (more than 2 minutes of footage) via media encoder 2019

this problem seemed to have occured only recently

My system configuration:

Windows 10 pro, nvidia GTX 670 (yes i need an upgrade) on latest nvidia drivers (as of 15/8/2019), 32 gb ddr4 ram

thx for the reply Wes. Disregard. It was a graphics card issue. Resolved.

I have used Insta360 however. what's the deal there?...

Nothing's changed on my end, same computer, workflow, and content. Here's what I get....

*Missing font messages

*Timeline freezes

*Unable to export a usable file

I'm mixing episode teasers, so mixed media jpegs, mov files, and png's. Adjustment layers and transitions. 3-5 minute files.

10 GB RAM devoted to Premiere

Updated drivers NVIDIA GEFORCE GTX 1050

Windows 10

Tried multiple fixes...

Shutting off font updates

Cleared Cache

Updated drivers

no joy

Yesterday I discovered that playback of 4k video (in premiere timeline) triggers an immediate spike in RAM use: RAM increases to maximum, followed by system crash. (I was working with proxies, but switched to the original file to make an adjustment).

System would not boot to windows after this. Had to have IT come in dig around to clear some error log, or some such.

Once operational, I tried recreating the issue. RAM started spiking as soon as I commenced 4k playback.

I was able to save and exit prior to crash.

(I don't have any photos in my project)

This has only been occuring since latest update.

System:

Win 10 pro

Premiere Pro 13.1

Twin Xeon E5-2680 2.4GHz

64GB RAM

Nvidia Quadro m5000

Thanks R Neil Haugen , I've reverted to Premiere 2017 now. Does anybody know if there's been any new progress on the issue?

Is there anything else I can do to help make some progress? If not, how can I keep track of the issue to know when it's fixed?

Wes Howell​

An interesting update from me: it seems that file size is a factor in triggering the crashes. I've been running a large number of tests, all with the 4k MP4 files that I usually work with. For the sake of consistency, each test consists of continuous playback of a single file, until either a crash occurs or the playback is finished.

For each test I have created a new blank project. In every project, there has only been one sequence which always uses the same settings (settings that I know work for my colleague who does not experience this issue with the same files.) I have only ever used one file per project. The codec, aspect ratio and acquisition method is constant for all of the files, which means that the only difference between them ought to be their size. What I have found that the smallest file I have tested (10 GB) will never cause a crash, whereas two larger files (15 and 20 GB respectively) will consistently cause crashes.

I have also observed a consistent pattern in performance indicators in my many tests. I have found that, for each file, the crash will always occur after a given amount of continuous playback, regardless of the point in the footage where the playback begins. Most of the time, though not always, the crash will then proceed along the following lines:

1. CPU and Disk usage will start to fluctuate erratically, playback will freeze.

2. Disk usage will suddenly spike to 90 or 100%.

3. Memory usage will begin to steadily climb towards 100%.

Ok so here is my update.  And I think I could be on to something now. The other day I was having a ton of problems with a really simple timeline on a large project.  Large meaning many sequences living within this project with a lot of different layers and text.  This was a brand new 1080 sequence using 1080 120p footage from sony A9.  Nothing magical or special here.  But Ram spiking like crazy and very laggy behavior.  So I called Adobe tech support.  Guy remoted into computer.  Turned off half my cores on my Threadripper. From 16 down to 8.  No surprise, computer crashed at some point while I was working. So I figured I needed to turn back on other cores.  They were not showing so I unchecked the box we checked to adjust this setting.  After that my computer would not boot.  Awesome!!!! I actually ended up having to re install windows 10 the other night.  Up till 4 am getting computer up again with programs needed to work.

So here was the big discovery.  I opened this project again to finish project.  And so many warnings popping up about fonts missing.  Soooooo many.  Fonts I thought were included in Windows.  But Adobe Type kit or whatever it is called now was not syncing.  So I got on my CC app and checked it. Tried to get to work and no luck.  So I turned it off.  All off it.  No syncing.  I also found a spot about syncing settings like workspaces to other computers.  I turned that off too.  I downloaded the fonts I needed from DaFont into my windows fonts folder old school method and computer is hauling ass now.  No lag at all.  In fact I am editing in a new project with Panasonic GH5 10bit 4k footage set up as vertical video for IG TV with no lag at all at 1/2 resolution. 

So is the Adobe Fonts thing an issue?  I started using about at some point last year.  And am not sure if I have really used after they changed the name from Typekit. I am guessing this is conflict.  Even when no fonts are present in your project they are present in PP.  Always syncing in the background.  Maybe it is Typekit fonts not working well with the new system?  Either way, I am turning it off.  It is causing too many issues and it is just easier to get fonts or buy fonts I need.  I keep having issues with the CC font stuff between PP, PS, and LR.  It is however cool they show up on Adobe Spark on my phone.  The tradeoff is not worth it.  I am keeping fingers crossed this was solution.

I have a Mac system with near identical specs to alvin_nari's original question and this issue started for me as well near the end of 2018. After downloading the 2019 update, my system starting crashing because Premiere would use the max amount of RAM available even though I'm editing the same kind of straightforward HD podcast video content I've been editing all year (much less complex than the more effect-heavy editing with 4K footage that my system has proven to handle fine in the previous months).

I've been using an older version of Premiere for a few months because I didn't have time to test the issue much, but that solution stopped working for me recently. Now I'm back to the most recent Premiere update (13.0.2) while running macOS Mojave 10.14.3 - and saw the same exact issues come back. (i.e. RAM overload and crashing)

I'm posting this here to let others know that it seems that deleting JPEGs does seem to fix the problem. I'm still in the midsts of testing, but things seem to be running smoothly and my system has not yet crashed. I will revise this post should that change.

Upon inspection, I did have Portrait Photos from a Google Pixel in my project file (as mentioned by jennya43632170). I'm not sure if removing specifically the Pixel Portrait photos OR all JPEGs fixed this issue, but posting this here in case it will help someone.

Here is update for me.  I need to work in an old project from last year.  So it was 2018PP.  I created a new project in 19PP then imported my old project with all of its files.  This is all simple non multicam stuff that I worked with last year no problem on this same system.  I opened one of my old timelines and guess what.  Horrific playback and memory off the charts.  This is totally nuts.  This is a bug for sure and this is getting old.  I have to make money.  And this is killing me.  No kidding I have spent days and nights and so much stress on this.  I am going to just try working in 18 and see what happens.  If this doesn't work I am going to lock myself to my desk and learn Resolve.  I can't keep wasting my life on this stuff.

This is again Gh5, Sony A9, Sony A7riii footage.  A mix of 1080 120p  4k 60p and 4k24p 

I figured out how to max out the RAM on my laptop with a "portrait mode" picture from my phone.

Just bought a Lenovo X1 carbon, intel core i7 8550U,16 gb ram, intel UHD 620 graphics, m.2 nvme storage, and I get this "maxed out modified ram" issue when I open a new project and add a single picture to the project. Tried updating windows, drivers, wiped Windows and reinstalled, reinstalled Adobe PP, and still adding a single .jpg from my phone crashes premiere. I kept dragging this folder of pictures and videos taken on my pixel 2 and getting this bug. My theory was maybe something about the portrait mode pictures was crashing premiere.

Open a new Premiere project. Everything is normal.

Add a normal .jpg file to a project, taken on my pixel 2. No memory ramp up. no new cpu usage.

add a "portrait mode" .jpg of my brother taken on my pixel 2, and immediately memory starts ramping up. Greater share gets taken over by "modified" RAM.

AAAAnd this is when everything starts to not work.

Takes over CPU, Memory and my disk.

If any adobe guys working on Premiere are at the Lehi office in Utah I can bring the computer by or send you the pictures that made it tick.