macOS 15 Sequoia Compatibility Issues Persist

[parkk74832512]

Last week, I accidentally allowed an upgrade to proceed, assuming there wouldn’t be any major problems. That was a mistake.

Constant crashes, clips disappearing without reason, ridiculously laggy preview scrolling, and processing that stutters for no apparent reason.

I’m having the worst experience I’ve ever had.

I tried updating Premiere Pro, resetting presets, and clearing the media cache, but nothing helped.

I wanted to downgrade, but too many processes have been completed since the update, and there’s a huge amount of data to back up, so I just don’t have the time.

It was my mistake to carelessly allow the OS update, but the repercussions have been massive.

If anyone reading this is considering upgrading their OS, absolutely DON'T do it right now.

[eliasmerzhaeuser]

I do have the same problem. It is completely unacceptable also from Adobe to deliver such instable and obviously untested software. There is no warning of this software not working on the OS... How is that not on the top of the priority list for the DEVs? Also it is a recurring experience.

Nothing more that furious for costing my time on top of that not so little money.

[Bertd]

The requirement page of Adobe is till not up-to-date since MacOS Sequioa still not on the list. Adobe is not sure either offcially I guess. To be mentioned release MacOS October 2024 and we live in February 2025! I hope it will work before the next WWDC25.

[cdavid1760]

It's may not be a Adobe issue if you have an M mac.. See my recent post on system level crashes and Sequoia.

[Sumeet Kumar Choubey]

Hi parkk74832512,

We're sorry about the poor experience. We can get this checked. Did the app become unresponsive, or did you receive a crash report? Also, please let us know the exact macOS version. We're here to help, just need more info.

Thanks,

Sumeet

[parkk74832512 · Accepted solution]

I’ve already deleted the OS and rolled back to the previous version, Sonoma, so I’m not entirely sure about the version. However, I had high hopes for the Sequoia version and kept it updated until November. I believe the current latest version is probably the same as back then.

[cdavid1760]

See my recent post on system level crashes, M Macs and Seqouia.

Here's the content of my post:

Heads-up: M3 Max Crashes with Premiere Pro under macOS 15.5 (Sequoia)

I've confirmed system-level GPU crashes when using Premiere Pro on macOS 15.5 (Sequoia) with an M3 Max MacBook Pro.

During scrubbing, timeline exports, or Metal stress tests, my system flashes red and reboots without warning or error dialog.

Here’s what I tested (June 17–19):
- :white_heavy_check_mark: CPU and memory stress tests = no crash
- :white_heavy_check_mark: Same drives/projects on Intel iMac = stable
- :cross_mark: M3 Max crashes under GPU load only (WindowServer, AGXMetalG15X-M1, QuartzCore in logs)

THIS ISN’T A PREMIERE BUG — the fault appears to lie in macOS Sequoia’s Metal/QuartzCore stack on Apple Silicon (M2/M3).

I’ve built a ZIP package with full crash logs, diagnostic scripts, and test configs. If others are experiencing this, I encourage comparing logs or referencing my report for escalation.

Premiere Pro: 25.4 (Beta, Build 54)
Chip: Apple M3 Max – 128GB RAM – 4TB internal
Drives: G-Raid, WD Black (ACSIS enclosure, TEAMGROUP 8TB (ACASIS enclosures)
Config: Tested both via Thunderbolt hubs and direct USB-C ports

[cdavid1760]

What are your system specs? Without that you're not telling us anything. This appears to be an issue with M macs and Sequoia. Under exact same circumstances no crashes with my Intel iMac. See my recent post about system level crashes under GPU intensive loads with M3M Mac and Sequoia 15.4. I've sent a bundled package, including crash logs and diagnostic tests and reproducible circumstances. I suggest you do the same to escalate the issue and get it fixed. I'm in the same boat with you needing to downgrade. I'll do it with Carbon Carbon Cloner and a TB3/4 Drive. If you decide to downgrade and use CCC (if it becomes too unberable (I have a CCC template you can use to bypass system backup.). 

Here is the content of my post:

Heads-up: M3 Max Crashes with Premiere Pro under macOS 15.5 (Sequoia)

I've confirmed system-level GPU crashes when using Premiere Pro on macOS 15.5 (Sequoia) with an M3 Max MacBook Pro.

During scrubbing, timeline exports, or Metal stress tests, my system flashes red and reboots without warning or error dialog.

Here’s what I tested (June 17–19):
- :white_heavy_check_mark: CPU and memory stress tests = no crash
- :white_heavy_check_mark: Same drives/projects on Intel iMac = stable
- :cross_mark: M3 Max crashes under GPU load only (WindowServer, AGXMetalG15X-M1, QuartzCore in logs)

THIS ISN’T A PREMIERE BUG — the fault appears to lie in macOS Sequoia’s Metal/QuartzCore stack on Apple Silicon (M2/M3).

I’ve built a ZIP package with full crash logs, diagnostic scripts, and test configs. If others are experiencing this, I encourage comparing logs or referencing my report for escalation.

Premiere Pro: 25.4 (Beta, Build 54)
Chip: Apple M3 Max – 128GB RAM – 4TB internal
Drives: G-Raid, WD Black (ACSIS enclosure, TEAMGROUP 8TB (ACASIS enclosures)
Config: Tested both via Thunderbolt hubs and direct USB-C ports

 

[parkk74832512]

I forgot to mention an important detail.

I'm using a MacBook with an M2 Max chip, 32GB of RAM, and a 1TB internal SSD.

[cdavid1760]

That's good information to have. I'm not for certain, I'm no developer, but if you are also on Seqouia then that may be the root of your issues per my post on GPU loads, crashes and Seqouia is the OS and not PP. There are other user platforms where people are talking about haivng issues with M Macs and OS 15 pointing to the OS being the issue and not the Software. Just food for thought.👍

[dougf42247315]

I bought a new m1 64 gigs ram, 10 core and several gpu cores to do work on a project coming from a similar ventura system running the premiere 25.3.  To link the 10TB of footage in several different folders, I'd have to do folder by folder and link by hand.  The M1 can't go backwards before it's shipping OS (15.5) and the prospect is so dauntint, especially as it may recurr if I have to pass the project along again, that the producer has put thet project no hold, maybe killed it.  This is totally unprofessional and makes me look bad as well.  Maybe that explaines the comment about people in here being rude.

[cdavid1760]

I'm so sorry to hear this. I wish I had a solution.