Premiere Pro crash error: "Your system has run out of application memory"

[Stephen384591249ysd]

I was attempting to open a project file in

Adobe Premiere Pro Version 24.5.0 (Build 57)

The project file is saved on:

Skandisk drive

Capacity 4TB

Available 2.09TB

Format ExFAT

The source files and the project files live on the same external drive.

When I unplug the drive from my editing partners MacBook and plug it in to my Mac mini to work on it. I get the following error before I am able to even view a loaded timeline:

"Force Quit Applications

Your system has run out of application memory.

To Avoid problems with your computer quit any applications you are not using."

The only application I have open is Adobe Premiere Pro 2024 (not responding) 99.03 GB

I was able to use Premiere Pro without it crashing when I was not using the drive.

The drive and the project file are not corrupt because they still work on my partners computer

My Computer: 

Mac mini Apple M2

Ram: 16GB

GPU

MacOS Ventura 13.5

Storage: 245.11 GB

Available: 187.05 GB

My editing partner’s computer

MacBook Pro Apple M2 Max

Ram 32GB

Mac)S Ventura 13.4

Storage: 994.66 GB

Available: 933.64 GB

[RjL190365]

Perhaps it's related to the quality control issues on all recent SanDisk external SSDs? These drives have a habit of failing due to a chip on the drives' circuit boards breaking off. And these drives cannot be properly repaired without wiping out all data.

[Carlos Ziade]

Based on RjL's technical reply, try to move the project locally and edit from there.

[Kevin-Monahan]

Hi @Stephen384591249ysd,

Thanks for writing the bug report. If the project is working on the more powerful Mac, then that may also be pointing to a performance problem. If you are editing a sequence with large frame-sized footage, like 4K or the duration of the sequence is on the longer side, that can also be a problem having less RAM.

We haven't heard back from you yet, so please let us know if you make any progress on the problem.

I am sorry for the issue.

Thanks,
Kevin

[Kevin-Monahan]

Hi @Stephen384591249ysd,

I am updating the status of this bug report.

Thanks,
Kevin