Participant

Question

Premiere Pro 2025 Crashes and Takes too much Volumes

Forum|Forum|1 year ago
October 19, 2024
42 replies
24408 views

Since the usage of premiere pro 2025, my mac crashes and freezes, since the volumes get to over 50GB, even though i am working with a very small project. It happens after a while and i dont know why. Never had this problem with the other Premoere Pro versions. I also cannot export. Very strange. I also have enough storage on my mac...

Show previous replies

S

stevel84653279

Participant

Recently upgraded to 2025 across all Adobe apps and seeing tons of lag. Premiere exports that typically take a couple of minutes showing as an hour. Other than rolling back, not really sure of a fix. Might finally be time to switch fully to Davinci.

A

andreas1701

Participant

I've had nothing but problems since the update... all of a sudden Premiere Pro is taking up any available resources (RAM, CPU) and my machine has crashed 3 times in the last 24 hours. Never had this issue before. I understand I dont have the top of the line here, but 32GB DDR5 RAM and an RTX 3050 shouldn't be so bad to the point where its unusable, especially for basic edits without anything other than a light color grade and the occasional blur and speed ramp here and there. Completely ridiculous.

A

Anilkumar Yadav

Participant

Today I used premier pro 2025 beta version for render a video, now
excellent performance with fast, smooth & buttery rendering video.

P

postmanRoulin

Participating Frequently

also happening in Illustrator and Photoshop 2025--crashing frequently. going back to 2024.

Vlady Valenti3710904582a6

Participating Frequently

Same issue here. Updated from Premiere Pro 24.6.3 to 25.0 and it has been crashing non-stop ever since. I'm on OS Sonoma. Quite annoying and tiresome. I switched from Davinci to Premiere due to a regular editing gig that made Premiere a requirement (because of mogrts connected to After Effects). I really like Premiere but these crashes are worrying me...

Vlady Valenti3710904582a6

Participating Frequently

Update to my post from yesterday:

I think I spotted the source of crashing in my case > Essential Sounds > Enhance Speech. I had played around with it and so it was enabled and loading everytime I was going through my raw footage. I removed all settings/sound presets from all my audio footage and so far no crashing. Maybe this is helpful for some of you out there.

D

Daisy34216439a6vi

Participant

Yes I've been noticing the same. It's the enhance speech that is causing my PR to crash and it also corrupts my file and I have to revert to an auto saved version. I guess I can edit my sound without using enhance sound but it does add a quality to my sound that I like.

D

Dawid33985840scse

Participant

Have the same Issues. PP crashing constantly. MacBook Pro M1 Max hier, Sonoma 14.6.1.

I event cant open a new Project with PP 2025. It crashing as soon as I save the Projectname.

Going back to 24.6 Version.

S

Sean27623129xpdk

Participant

Am in the middle of huge documentary project - several timelines filled with many hours of 4K footage - updated to PP 2025 and immediately ran into major issues. Takes forever to load. Have read everyone notes and tried all suggestions. No change. Just waited 45 minutes for it to fully load all the audio in my sequence - and so i've just now switched back to 2024 - but gonna lose 2 days of work that i put into the 2025 version. So much uncertainty. Search for stability is ever ongoing and safety is an illusion. As Whinston Churchill put it "Keep Buggering On!"

iMac 5K, 27-inch, 2019

Processor: 3.7 Ghz 6-Core Intel Core i5,

Graphics: Radeon Pro 580X 8 GB

Memory 32 GB 2667 Mhz DDR4

macOD: Sonoma 14.6.1

J

Jamie36068236qgf7

Participant

I just reset preferences, cleared the cache, plug in cache and disabled third party plug-ins. Seems to be working ok for now!

S

Sfearman

Participant

My issue is it takes forever to load up (more than 5 mins sometimes. I haven't rendered anything yet on 2025 but I am going to try this afternoon with a 3 min video with minimal effects etc. I have a RTX 4070 SUPER, 128 gb ram, 19-9900, 3.6ghz, running windows 10 Pro...no excuse for this.

A

antumartin91

Participant

Same issue on Macbook M3 Pro 18gb and 1080p multicamera project. Constant crashing and low memory alert. Same kind of projects doesnt make any problem on Premiere 2024, its annoying

T

tylerr7

Participant

Has anyone found a fix to this problem yet? My premiere won't stop crashing whenever I bring footage into a new project. I've tried rolling back to premiere 2024 and it's having the same problem. 2024 was fine for me before but now it's crashing the same as when I updated to 2025. I don't know what to do, I have clients waiting for videos and I'm unable to open projects for more than a couple minutes before they crash. This is absolutely unaccaptable. I may not have another choice than to switch to Davinci or Final Cut and I really don't want to but I'm not the last straw with adobe.

leem95275565

Participating Frequently

On a M3 Ultra Macbook Pro. Premiere automatically updated to 2025 and it made me resave the projects I was working on. The program crashes every 20 minutes. I've put hours into this edit and now I need to revert back to the last version but I don't know how to get this save file to open in the new program.

Warren Heaton

Community Expert

@leem95275565

When Premiere Pro 2025 prompted you to save your 24x version project as a 25.x version project, you should have noticed that the filename was the same with an “_1” appended to it. If you proceeded to save at that point, then you have both the 24.x project and the 25.x project. For example, for a 25.x project named “Upgrade Best Practices_1.prproj” there would be a separate 24.x project named “Upgrade Best Practices.prproj”. As long as Premiere Pro 2024 is still installed or is re-installed via Creative Cloud Desktop, the 24.x version of the project file should open as expected.

If the “_1” was removed and you saved over the 24.x version then it is now a 25.x version project file; however, if you have not worked for too long in Premiere Pro 2025, then most if not all of the auto-save projects should be version 24.x. Try opening the auto-save project files in Premiere Pro 2024 from newest to oldest.

So that you don’t accidentally open a 24.x PRPROJ file in Premiere Pro 2025 again, be sure to set the “Open With” option for Premiere Pro project files to Premiere Pro 2024 in the Info dialog box (File > Get Info) while any PRPROJ file is selected in the Finder.

In your Creative Cloud Desktop application, it sounds like you want to make sure that Auto-Update is disabled and that “Remove old versions” is disabled. With that set, you’ll receive an alert to update to a new release and when or if you do, you’ll always have the release that you were using (in this case 2024) installed along side the new release (in this case 2025).

Continue to work in Premiere Pro 2024 until you resolve what is causing the crash in Premiere Pro 2025. You mentioned that you’re on an “M3 Ultra MacBook Pro”. It must be an M3, M3 Pro, or M3 Max as there is no M3 Ultra MacBook Pro. With an M3 based MavBook Pro, a likely cause of Premiere Pro 2025 not working as expected is a conflict with a third-party plug-in, extension, or add-on. A troubleshooting step would be to check to see if updates are available for those. Another thing to try it to start a new, empty 25.x version project and then import your 24.x project into that. When saving, be sure to include something in the 25.x version project filename that makes it easy to differentiate it from the 24.x version project. For example “Upgrade Best Practices pr24.prproj” is a good name for a version 24.x project file while "Upgrade Best Practices pr25.prproj” is a good name for a version 25.x project file.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded