Premiere Crashes Randomly

Forum|Forum|1 year ago
October 15, 2024
3 replies
968 views

I had several problems after updating my MacBook Pro M1 Max to Sequoia 15.0, with Premiere crashing every 2 minutes - and sometimes on startup when there was some Chromatic Aberration/Turbulent Displace at my playhead.

I tought the pain was over after the new 2025 Update but it's even worse. I can't deliver a project I'm working on cause I can't open the project. It's embarassing.

Is it a CPU problem? does anyone else have the same problem? I was thinking about upgrading - even though i have a maxed out M1 Max - but I want to wait till M4 comes out.

This topic has been closed for replies.

Dtor

Participant

same for me 2024 was working fine then when I switched 2025 it crashes so uch. at least now theres a crash recovery folder that pops up in the auto-save folder but its slows the work flow. try saving and opening in 2024:

Open Premiere Pro 2025 and re-save the project in a format compatible with 2024:
- Open the project in Premiere Pro 2025.
- Go to File > Save As and rename the project.
- Export the project to XML:
  - Go to File > Export > Final Cut Pro XML or AAF format, which is compatible with older versions.
Open in Premiere Pro 2024:
- Open Premiere Pro 2024.
- Go to File > Import and select the XML or AAF file you exported.
- This should open the project, but some effects or features exclusive to 2025 may not fully transfer.

Ishan Y

Inspiring

Hi there,

I'm sorry to hear about this. Do you see the crash reporter window when Premiere Pro crashes? I recommend granting full disk access to Premiere Pro (System Settings > Privacy & Security > Full Disk Access) and trying to launch Premiere Pro with third-party plugins disabled (https://adobe.ly/3BUh4my). Let us know how it goes.

Thanks,

Ishan

F

Fabrizio26965871dnbrAuthor

Participant

I don't have any plugin installed, and yes it has full disk access. It randomly crashes on startup even when I clear the cache. I don't even have the time to switch to a "simpler" sequence.

I tried to test the same project with a M3 mac and it didn't crash..could it be something with hardware/gpu acceleration? It's a strange guess considering that it's the same architecture but I don't know what to do.