Skip to main content
Known Participant
June 27, 2024
Answered

100% disk access and 100% RAM usage for no reason, completely blocking my ability to work

  • June 27, 2024
  • 67 replies
  • 6628 views

Show-stopping performance issue here! I am completely blocked from being able to work at all. Premiere is currently using 100% disk access and 100%+ memory usage, sitting idle, doing nothing!

 

In Premiere Pro 2024, I opened a project originally created in v2023. Was prompted to convert the file format. After doing so, disk access on the drive where the video files are stored immediately skyrocketed to 100%. It stayed that way for a very long time. Two hours later, the drive was still being hammered to death. Completely unable to use Premiere at all, it was dead in the water because it couldn't play any files. CPU usage was near zero.

 

Resource Monitor showed Premiere reading the source footage files. If it was trying to build peaks and caches, it did so with extreme inefficiency.

 

Even worse, after closing the project, disk access persisted at 100%. Resource Monitor showed the same few source footage files being read. Eventually Premiere got tired I guess, or it felt it had punished the drive enough, and eventually petered out after about five minutes.

 

Other projects opened normally, there were a few seconds of heavy disk access but then it went back to normal -- zero access when Premiere is idle.

 

Of course I restarted the Windows 10 PC, but that made no difference.

 

Updated to 2024.5, re-converted the original v2023 project file, but that made no difference.

 

Deleted all Media Cache files through Preferences, but that made no difference.

 

I did notice that projects using footage encoded with Blackmagic MJPEG codec hit the drive a lot harder than projects using footage encoded with NVIDIA NVENC H264. I guess H264 files don't need caches at all?

 

The problematic project has about 100 source files, TRT 14 hours, all encoded with Blackmagic MJPEG. Totaling about 400GB, which is kind of a lot, I know. It's showing them all as offline while it hammers the hard drive, presumably trying to build caches and peaks. So one might conclude that there's a performance issue with the codec? It's not hardware accelerated. But there was no issue whatsoever when I originally edited this project in Premiere 2023. And again, CPU usage is near zero, so the problem seems to be completely about hard drive access.

 

Contrast this with another project using the same codec, with only ten files totaling 3GB, TRT 30 minutes. Even after deleting all cache files, the smaller project takes ~15 seconds to load. The larger project does not finish loading even after two hours. The math here doesn't seem to add up. I could imagine that 400GB would take a half hour at most. Not multiple hours.

 

I did update the Blackmagic Desktop Video software, which includes the MJPEG codec. Not really relevant, though, because Premiere has native support for MJPEG. It just won't load the audio in the AVI files created by Blackmagic unless the Blackmagic codec is installed. Not a concern for me here because I'm not even using that audio. But updating the Blackmagic software made no difference.

 

Any way you slice it, a project should not take hours to load, even if the source footage is 400GB. I am really not accustomed to this sort of behavior. Sony Vegas never made me wait for hours while it ground my hard drive to dust, no matter how large the source footage folder was. If this is supposed to be speeding up my workflow, I regret to have to say that it is the opposite of that. It has completely shut me down.

 

I really don't want to erase my preferences, since it was a huge PITA to get Premiere set up to be even remotely close to an efficient workflow.

 

So what am I supposed to do here? Reinstall v2023? I doubt that would make any difference, as it seems the issue is just massive inefficiency in building the cache files.

 

Is there any option to NOT build these cache files? Or to control how many files are read simultaneously? Maybe if it was only reading one file at a time it wouldn't be fighting itself for limited bandwidth?

 

BTW, the hard drive is not super fast, but it is a 7200 RPM Western Digital platter, internal. Again, if I were to do a backup, I would expect that 400GB would take maybe a half hour to transfer. Not multiple hours!

 

And why are these caches temporary external files in the first place? If they take so long to build, shouldn't they be persistent? If not stored in the project file, at least stored next to the source footage? That's an option for the peak files. Why not the cache files? Why set things up for failure like this?

 

In the end, I let the computer sit for hours until the disk access went back to zero. All of the footage in the bins finally read as being found, not pending, and all of the statistics were visible. Tried to access the timeline and BOOM, disk access went back to 100%. What the actual frak?!?! And now RAM usage is pegged at the maximum, too! I have 32GB RAM and have 6GB reserved for other applications. Premiere has gone totally rogue here, consumed 100% of disk time and 100% of memory. Now it's using the page file, completely runaway process, it's currently up to 44 GB and still rising. SITTING IDLE, DOING NOTHING.

 

I turned off the timeline thumbnails with the super secret hotkey. No change. Disk access still pegged at 100%. RAM usage still greater than the maximum I set aside for Premiere. What is Premiere even doing? It's not building caches, it's not playing the timeline, it's just sitting idle. This is OUTRAGEOUS! Resource Monitor says it's still accessing those source files. But WHY???

 

How do I get back to being able to actually work?

 

This is just shocking!!! It's acting like malware!

Correct answer andrzej_1443

Hello everyone.

I uploaded Premiere 2025 today. It looks like the disk problem has been 100% fixed. Same computer, same configuration. I didn't change anything. It turns out that the problem was in the Premiere 2024 software. This is the worst situation I've ever had with Adobe. It cost me a lot of time, nerves, searching for a solution to the problem, which made work very difficult and prolonged. It was a serious software error. I hope that nothing so significant will happen in the future. Adobe, please give me another month of use for free! Either way, I consider Adobe software and the Premiere program to be a very, very good work tool. I started my adventure with Premiere with Premiere 6.5. It continues to this day!

67 replies

R Neil Haugen
Legend
June 27, 2024

First, never uninstall when adding a new version. Always keep the previous versions installed for continuity and safety sake.

 

Second, I assume you've created new projects in 24.x, and this happens across multiple new projects?

Everyone's mileage always varies ...
Known Participant
June 27, 2024

OK, so I closed and reopened Premiere, and the "Relinking Media" process started all over again, as if it had never happened at all. Something is very seriously broken here.

Known Participant
June 27, 2024

As I explained, this project worked fine in Premiere 2023. I don't think it's reasonable to blame the Blackmagic hardware or software. It's an issue with Premiere.

I let Premiere grind my hard drive to death all night. Even though there were no more cache files to build, and the Progress window showed no activity, Premiere hammered the drive for many hours.

Then, the next day, I saw that the hard drive access went down to zero. But the instant that I tried to access the timeline, the hard drive access went back up to 100% and stayed there.

Under no circumstances is it acceptable for an application to greedily consume all system resources for such an extended period of time. The irony is palpable: cache files being built to speed up performance ... completely halts the functioning of the computer.

For future projects I will test out different options. The MJPEG codec is kind of necessary, the only other options are either way too disk-heavy or cause visual artifacts. Maybe I can batch convert these files to something Premiere can reliably handle? H264? ProRes?

Otherwise I will have no choice but to abandon Premiere. Because this is absolutely not working.

I guess I can also try to uninstall and reinstall a fresh copy of Premiere, or reinstall v2023. But seriously, this is horrible, heartbreaking, infuriating, and demoralizing.

R Neil Haugen
Legend
June 27, 2024

I would suggest the possibility that something in the installation or operation of that capture card creating the files is ... mis-happening, let's call it. And that that problem is causing the issue in Premiere.

 

Is that a possible problem?

Everyone's mileage always varies ...
Known Participant
June 27, 2024

I broke down and reset all preferences and deleted all media cache files. No improvement. Hours and hours wasted.

Seriously, this is just horrific. Eating up 100% of disk time and more than 100% of RAM, for no reason. Progress window says nothing is happening, but the reality is that Premiere has completely borked the system.


I may have to switch back to Vegas, render everything to uncompressed and then compress it with Media Encoder. Because I cannot waste my life like this.

Known Participant
June 27, 2024

It's a PCI capture card

R Neil Haugen
Legend
June 27, 2024

What camera is that? I'm running BRAW and ProRes from my BM cameras, I've no clue what that mjpeg media would be.

Everyone's mileage always varies ...