Skip to main content
Participant
October 2, 2025
Question

Premiere Pro issues with macOS Tahoe 26.0

  • October 2, 2025
  • 5 replies
  • 2070 views

I've been noticing several issues since upgrading to the latest mac OS, Tahoe 26.0.

 

Aside from general bugs (timeline unresponsive to hitting spacebar/play, shutting down unexpectedly, general lagging), the biggest issue is I am unable to export my timeline. Both the keyboard shortcut, File > Export > Media, and the selecting Export option at the top of the program screen do not bring me to the Export menu. It only works when selecting File > Export > Send to Adobe Media Encoder. 

5 replies

alfredobarros
Participating Frequently
February 5, 2026

CRITICAL Memory Leak: Premiere Pro v26.0 on macOS 26 (Tahoe) - 89GB+ VM_ALLOCATE Exhaustion
 

Summary: I am reporting a severe memory leak in Adobe Premiere Pro 2026 (v26.0.0.72) running on macOS 26.2 (Tahoe). The application progressively consumes all available physical RAM and exhausts swap space until the system becomes unresponsive or forces a hard crash.

This is not a standard "high usage" scenario. System logs confirm that Premiere is allocating untagged virtual memory without releasing it, forcing a SIGKILL or manual termination.

System Specifications:

  • Hardware: Mac mini (M4 Pro)

  • Memory: 48 GB Unified Memory

  • OS: macOS 26.2 (Build 25C56)

  • Premiere Pro Version: 26.0.0 (Build 72)

The Issue: While performing standard editing tasks (proxy workflow, no heavy VFX), Premiere Pro's memory footprint expands uncontrollably. In my most recent crash, the application reached 89.14 GB of memory usage on a 48GB machine, forcing the macOS kernel to create an 80 GB Swap file.

Technical Analysis (from sysdiagnose/footprint logs): I have analyzed the footprint-all.txt and JetsamEvent logs generated during the freeze. The culprit is undeniable:

  1. Untagged Memory Allocation: The logs show 84 GB categorized as untagged (VM_ALLOCATE). This indicates that the Premiere engine is requesting raw memory pages from the kernel and losing the reference/pointer to release them.

  2. Swap Thrashing: The system was forced to swap 80 GB to the SSD to keep the process alive.

  3. Kernel Response: The system triggered a vm-compressor-space-shortage Jetsam Event.

Troubleshooting Steps Taken (Issue Persists): To rule out external conflicts, I have performed the following:

  • Clean Environment: Removed all third-party Endpoint Security software / Antivirus.

  • macOS UI Tweak: Enabled "Reduce Transparency" in System Settings > Accessibility to mitigate potential WindowServer memory overhead. While this slightly lowered system pressure, the specific VM_ALLOCATE leak within Premiere remained unaffected.

  • Peripherals: Disconnected all DisplayLink adapters and monitors (suspected WindowServer conflict, but the leak persists purely within the Adobe Premiere Pro process).

  • Preferences Reset: Cleared Media Cache and Preferences.

  • Memory Limiter: Setting the "RAM reserved for other applications" to a higher value (leaving only 24GB for Premiere) temporarily delays the crash by forcing more aggressive garbage collection, but it does not stop the leak.

Conclusion: There is a fundamental regression in memory management between the Premiere Pro 2026 engine and the macOS Tahoe memory compressor. The application is failing to release VM_ALLOCATE pages.

I am available to provide the full .ips and sysdiagnose logs to the engineering team if required. This is a production-blocking issue.

Regards,

Alfredo Barros
Professional Editor
 

 

System Specifications: - Hardware: Mac mini (M4 Pro) - Memory: 48 GB Unified Memory - OS: macOS 26.2 (Build 25C56) - Premiere Pro Version: 26.0.0 (Build 72)
alfredobarros
Participating Frequently
February 5, 2026

I forgot to mention an important thing about my project:

Project Origin: Legacy project originally created in Premiere Pro 2025 and migrated/opened directly in v2026. While performing standard editing tasks (proxy workflow, no heavy VFX) in Premiere 2025 using OS 15 Sequoia, it was working fine.

System Specifications: - Hardware: Mac mini (M4 Pro) - Memory: 48 GB Unified Memory - OS: macOS 26.2 (Build 25C56) - Premiere Pro Version: 26.0.0 (Build 72)
Averdahl
Community Expert
Community Expert
February 5, 2026

@Averdahl @Averdahl Try to create a new project in V26 and then import the old V25 project into the new project. Importing old projects instead of converting them is often better so it´s woth trying. Be patience, it can take a couple of minutes.

Participant
November 19, 2025

I have been experiencing the exact same issues since I updated my OS. I have the most up to date version of Premiere and it's been so frustrating to try to work on projects. 

Community Manager
November 20, 2025

Hi Justin243055456iba,

 

We're sorry to hear about this. We will get it checked. Could you please confirm whether you are experiencing lag while interacting with the UI, or if it's a playback performance issue? Also, please let us know the exact version of Pr & the OS that you are using.

 

Thanks,

Sumeet

Participant
October 25, 2025

"Aside from general bugs (timeline unresponsive to hitting spacebar/play, shutting down unexpectedly, general lagging)". This is my biggest issue. I'm on Tahoe 26.0.1 and Premier Pro version is 25.5.0 (Build 13). Really annoying since it get unresponsive sometimes up to 30 seconds. I should have waited a month before updating to Tahoe (I normally wait a month or two when a new OS is released). 😞 

Participant
October 2, 2025

Hi Dani,

I am on version 25.5.0, Build 13.

I am also able to use Project panel > Export Media as well. The problem seems to stop when I restart my computer, but then will occur again, maybe an hour or so after using Premiere. I have yet to test it on another project.

Thank you for your help,

KELLY PAOLI
( she | her )
Director | Filmmaker | Editor

[Personal Information removed by moderator]

Community Manager
October 2, 2025

Hi @kellyp38581716

Welcome to the Premiere Pro forums and thank you for reporting a problem. Can you confirm the Premiere Pro version you are on? Is this happening with all you projects or is this project-specific? 

Are you able to right-click your sequence in the Project panel > Export Media from there? What if you change or reset your workspace? 

Sorry for the frustration, 
Dani