Skip to main content
dsfsdfsdfsdfs
Participant
December 12, 2024
Answered

Premiere Pro using 99% of CPU whenever I make any adjustments to my project

  • December 12, 2024
  • 3 replies
  • 641 views

I'm having an issue where whenever I try to edit my project it either causes my computer to crash or uses up 99% of my computer's CPU. This only seems to be happening with one of my projects that uses a lot of OBS screen recordings.

 

Here's the information asked for in bug reports:

App Version: 25.1 (also happened in all the 24 versions of the app)

Platform: Windows 11 with 32 GB of CPU. Uses a NIVIDA Studio Driver

Steps to cause issue: Make any changes in timeline or effect controls.

Expected result: Make the change

actual result: Makes the change, but used 99% of RAM 

 

I've already tried doing all of these things that Peru Bob mentioned in a similiar post:

"Try resetting the preferences:
https://community.adobe.com/t5/premiere-pro/faq-how-to-reset-trash-preferences-in-premiere-pro/td-p/...

If that doesn't work, try resetting the Workspaces:
Reset a workspace
Reset the current workspace to return to its original, saved layout of panels.
1. Do one of the following:
• Click the Workspace menu icon and select Reset to Saved Layout.
• Choose Window > Workspace > Reset to Saved Layout.
from here:
https://helpx.adobe.com/premiere-pro/using/workspaces.html

If that doesn't work, try Preferences > Audio Hardware and set Input to None.

If that doesn’t work, try updating or rolling back your graphics driver directly from the video card manufacturer’s site. If NVIDIA, do a clean install of the latest Studio Driver (NOT the Game Driver).

If that doesn't work, try creating a new project and import the old one into it."

 

Thanks so much in advance!

This topic has been closed for replies.
Correct answer R Neil Haugen

So this only happens with one Project?

 

Project files can get corruption in them, and to 'fix' that it's normally you create a new project, and in the MediaBrowser panel (while in the new project) ... you select the old project file, and one by one import sequences to the new project.

 

After each one check for how that sequence works in the new project, if fine, add another one.

3 replies

R Neil Haugen
Legend
December 13, 2024

Thanks for replying with the information about what happened and how you got going. That's always useful on a thread.

Everyone's mileage always varies ...
dsfsdfsdfsdfs
Participant
December 13, 2024

Thanks for replying, it really helped me figure out the issue. The issue was that I had a sequence with 400 layers (I went a little over the top) and that was cauding the issue. I rendered a replaced that sequence and that fixed it.

R Neil Haugen
R Neil HaugenCorrect answer
Legend
December 12, 2024

So this only happens with one Project?

 

Project files can get corruption in them, and to 'fix' that it's normally you create a new project, and in the MediaBrowser panel (while in the new project) ... you select the old project file, and one by one import sequences to the new project.

 

After each one check for how that sequence works in the new project, if fine, add another one.

Everyone's mileage always varies ...