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

Known Participant
July 5, 2024

There is also a problem with DV AVI videos...

Known Participant
July 4, 2024

I cannot download any version of Premiere, or any other major CC subscription app, that is more than two years old. Unless there is some super secret archive of old installers. Make with the links.

If I had a time machine, then I would go back and tell myself not to uninstall anything. But then what happens when this machine dies or needs its OS wiped?

Corporate policies are getting in the way here. No question about it.

Peace out

R Neil Haugen
Legend
July 3, 2024

There are several million daily users of Premiere Pro, many for broadcast/streaming and corporate web work. They are working without issue. So those with problems are not the vast majority, and that's something a lot of users struggle with understanding, That said ...

 

First, there shouldn't be any issue with multiple major versions installed. Most of us long-time users advocate never uninstalling a version. This machine has back through the 2019 versions installed, PrPro, Ae, Au, Me, and others. My old (now 'backup') machine has clear back to the original CC and CC2014 versions ... including SpeedGrade, alas ...and yes, I occasionally do take something into SpeedGrade for specific uses.

 

And I've never had an issue with that practice.

 

As to the comment that "we're not allowed to run versions more than two years old" ... balderdash. You can run any version you have installed. I and many others do routinely.

 

Next, subscription or not isn't actually an issue either. I've got software from both subscription and purchase, and they all can and do have bugs. Was it easier years ago to produce software with fewer bugs? Oh Hades, yes.

 

There were far fewer pieces, makes, and mods of hardware and OS out there back then. For another example, as BlackMagic has been working at turning Resolve into an Adobe clone, "one ecosystem for all video post" ... they've been having more bugs and odd behaviors across their user base. And yes, I work daily in Resolve, and am also active over on the BM forums, plus I teach pro colorists via the MixingLight website ... mostly based in Resolve.

 

Resolve is simply a loss-leader for BlackMagic, it's a way to get us hooked into their system to buy their hardware. Like many others, I've got enough BM hardware to have several licenses in a drawer here. They ... don't make it easy, at all, to use non-BM hardware with Resolve. Not because they're evil or greedy, but because that's how they make a living.

 

Subscription is the same way. It's neither good nor bad, simply one model to make a living for those employed by a company.

 

The only pretty much bug-free video post app I know of is Baselight. How do they do it? Old-school.

 

You buy the computer from them, with all allowed software installed, for between $14,000 and $20,000. For the computer alone. You NEVER EVER add another app or utility to that computer.

 

Next, you pay a couple thou a year for a license to use the app on that computer. And yes, for that you get an awesome app that is rock-solid stable. Of course, if you need to go setup in another studio for a week, you must dismantle and pack your system, move it, and set it up there.

 

Companies are simply groups of humans. Humans by nature are both incredibly variable and freaking all over the place. No two groups will ever come to the same list as "the important things!" let alone design the same setup. I have talked with a lot of Adobe supers and devs, and well, many of my 'big things!' are bluntly going to be used by too few people to have a chance at being incorporated. Yet a few have been.

 

Same with BM, although I don't personally know any staffers there. I've talked with enough of them at NAB/Vegas for a decade to hear pretty much the same comment. Ah well, right?

 

And understand, I understand the frustrations using any and all of these applications. Ain't none of them perfect. So I've learned to adopt a very practicality based attitude ... what gets the work out the door, works. Do that, whether I emotionally like it or not. Keep the emotions out of it or you'll go nuts.

 

And use whichever of the Fancy Hammers works ... as that is all any of these apps are, fancy hammers. I don't waste a moment of emotions on a hammer.

Everyone's mileage always varies ...
Known Participant
July 3, 2024

Thanks, I already tried updating the Blackmagic drivers and installing 2023.0. Maybe I also need to uninstall Premiere 2024.5? But I can't do that because I have active projects that require that version. Unlike Maya, I don't believe Adobe project files are forward compatibile across major numbered releases.

It just goes to show the deeply problematic nature of the entire paradigm of constant updates. Even if the updates aren't forced, they introduce all manner of bugs and incompatibilities. The only solution to those is more updates. Which introduce new issues that require more updates. Gone are the days of a software application being released as free of bugs as possible. Stability is a thing of the past.

Then add draconian policies around subscription models, and it's a recipe for disaster. We're not even permitted to run any version of Creative Cloud subscription apps more than two years old.

All of this is decidedly hostile to getting any real production work done. Forget about revisiting an old project. It's very likely to be inaccessible. And with a complex project, I don't even know how we can work around that. Archiving is a disaster. We might as well go back to film and tape; many of the benefits of nonlinear editing have been negated by these horrible corporate policies and practices.

Participant
July 3, 2024

Rather than disc access i still things is related to the clips.  Have you seen this thread: https://community.adobe.com/t5/premiere-pro-discussions/cannot-import-an-avi-project/m-p/14717576#M511927

MyerPj
Community Expert
Community Expert
July 1, 2024

It's nothing more than a inflexible folder arrangement, which extra processing needed to manage the partitions. The HDD Head has to move back and forth from the partitions. And there is absolutely no advantage to backing up to a partition, if the HDD goes, all the partitions go. That totally defeats the purpose of backing up. You might as well just do it to a folder.

 

If you are partitioning to have a different OS for testing, or use otherwise, a case could be made. But HDD and SSD are pretty inexpensive these days so, pickup a new drive and use that for backup and even a different OS.

Known Participant
July 1, 2024

Honestly, the partitioning scheme I use is more for my own organizational process than anything else.

R Neil Haugen
Legend
July 1, 2024

I'm used to using folder structures for organizing like that. And none of the backup software I know of has any issue with abiding by folder directed work. I assume I'm not familiar with your backup software.

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

There are other reasons for partitions. Actually I never even heard of the idea that they would improve performance.

Mainly, it's for convenience and time savings. Partitioning is helpful for me to organize my data. Splitting a 14GB platter drive into three partitions helps me keep my data in a logical framework. It also helps with backups. By keeping data in different partitions, I can, for example, back up active projects while leaving archived projects alone. This saves a lot of time, because the mirroring software I use needs to parse the entire job on both the source and target drives before it does any transfers. If it had to read all of the data on a monolithic partition, it would take way longer.

Known Participant
June 30, 2024

Seriously, how could throttling the CPU help prevent excessive disk or RAM access?