Participant

Question

Memory leak/out of memory - Ryzen 1700X system

Forum|Forum|9 years ago
March 15, 2017
5 replies
3581 views

Hey!

I bought 2 days ago a Ryzen 1700X CPU with a Gigabyte X370 Gaming 5 motherboard to use, among other things, for Premiere Pro.

I have tried all possible things and I can't get it to work properly, because of EXTREMELY fast "out of memory" behavior. So I have 16GB of RAM on my machine and if I import 20 4k video files, there's an 80% chance it will run out of memory during import, or a 100% chance it will run out of memory during conforming. The entire process takes around 30s and then Premier Pro is dead. It either closes itself, or I get the out of memory warning with a lot of errors reported by PP itself, cautioning me to save the work and close the program.

I tried CUDA acceleration (GPU accelerated Mercury Engine) and software both. They behave the same. The lockup with CUDA enabled is more severe, it may even make the NVIDIA drivers crash. This is on a GTX 1070. Also tried with an RX 480 and it behaves the same, although there's no driver crash.

I have tried with a fresh Windows 10 install, same behavior. Thought it might be the (already fresh, since it's a new system) OS, but that's not it.

Have disable Intel h.264 accelerated decode. Have played with the memory settings allocating more or less GB to PP and selecting to optimize for Memory, not Performance. The same!

It is most clearly PP. Have even tried with an older version (11.0.1) and still the same. Even tried with Windows 7, completely other OS, new install etc. And the behavior is exactly the same. I still have my old system, an Intel i7 6700K and while it eventually does run out of memory after 1hr or working on very big projects, it doesn't gobble up the 16GB of RAM almost instantly. When conforming on the Intel, RAM rises, then drops a notch, then rises, the drops. On the Ryzen it just rises until there's no more room.

The conclusion is that I cannot use my new system with PP, which is pretty damn disappointing considering that this is kinda the main reason I built it.

Adobe, please look in to the issue with Ryzen memory problems or try to give me a solution cause I'm going mad here...

[moved to hardware forum by mod]

This topic has been closed for replies.

F

frankt54142677

Participant

Hi, your problem is your memory, you must use G.Skill Flare or Fortis, they are made with Samsung B-Die chips (single rank), the only one, apparently, that is compatible with speed at 3200MHz for ZEN platform. Sure in a short time all memory's will be 100% compatibles but for now, that is what you need or down the memory speed in BIOS, testing to find a stable speed below 3200MHz. Sorry my bad English and hope this will help you.

A

Anonymous

I can report the same issue.

I have a Ryzen 1800x, 32gb (2x16) Corsair vengeance 3000hz.

My ryzen is updated to the latest F5 bios.

I am not overclocking (aside from the stock boost).

I am getting out of memory errors during renders. Generally happening when I am rendering in the background and doing something else like web browsing or watching video (not streaming).

I can clearly see (with a number of applications) that I have at least 10gb available when I get these errors.

It seems to be effecting Photoshop and Media Encoder too. I don't use any other adobe apps so can't comment on anything else.

I also have a Samsung Evo m.2 SSD running on 4 of my PCIe lanes.

I am not experiencing this issue with any other applications, including 3DS and Lightwave which are resource intensive when rendering.

content_creator_07_13Author

Participant

I'll come back with the benchmark results as soon as I can - the system is not running anymore since I can't use it. I'm on my previous Intel system now.

System specs:

Ryzen 1700X CPU

Gigabyte X370 Gaming 5 motherboard

Radeon RX 480 GPU

16GB 3200MHz G.Skill TridentZ memory

3TB of HDD storage (this is NOT used for PP, just raw storage)

More than 1 TB os SSD storage (SATA3, not PCIE) - this is used for other stuff, but I have 60GB dedicated for a single project (current project I'm working on in PP), and a 20GB separate cache partition).

Up to date Windows 10 and all drivers.

We're talking importing 20-30 GB max of 4k files. That's around 15-30 files depending on length. I don't see how this could be an issue for PP if it would work correctly.

I tried yesterday to open a previous project that has around 28GB of used video files and it gives me an out of memory message within 10s of opening it. RAM is going like this: 0.5-1.5-4-6-7.5-9-10.5-12-13.5 boom, crash. That 10s worth of time.

I'll repeat the behavior on the Intel system with the same project: slowly shoots up to 7-10GB then has a quick drop to 3-4GB, then goes up again. So it doesn't crash by doing this.

Bill Gehrke

Inspiring

Well we need more information on your hardware, what, how many and how are you using storage devices for premiere?

I would sure like to have you run my Adobe Premiere Pro BenchMark (PPBM) which has been successfully run 1000's of times and let us know your results

content_creator_07_13Author

Participant

Hey!

Finished with the benchmark. Hope this helps, alongside the other information I gave earlier. Support is GREATLY appreciated!

Bill Gehrke

Inspiring

Well the results are not giving me any clue to your memory leak problem Since these four exports in PPBM ran satisfactory.

Unfortunately your 8-core 16-thread Ryzen at the normal turbo speed of 3,6 GHz gave us 550 seconds for the CPU intensive test and that puts it in the 4-core 8-thread Intel class of processors. I will add it to my list.
Your 32 seconds for that same timeline with GPU acceleration with your Radeon RX 480 is quite typical of an AMD GPU See my GPU data
Your 77 seconds for the Disk intensive export puts in the typical SATA III SSD category see thsi data
Your 97 seconds for the H.264 timeline export which is both CPU and GPU intensive is nothing exciting, see that same GPU chart as above for the results on my much more expensive 8-core Intel system.

Sorry I can not give you any solution to your memory leak but at least these 3 timelines are working properly but not very excitingly.