AE to 25.01 - Error/crash related to rendering (and upgraded projects?)

[Oguz_KALENDER1662]

After effect updating AE to 25.01, it keeps giving errors and crashing, I can't do anything, I can't render. I'm about to go crazy, please someone help me, I deleted and reinstalled it many times but the problem didn't change.

[Silvain Fuchs Pro]

Hi all,

is there any update or solution on this matter?
I've been experiencing the same problem since I updated AE 2024 to 2025.

MacBook Pro 14-inch, 2021
16 GB ram
macOS Sonoma 14.7.1

[Capvel Martain]

Hello same for me for a couple of AEP files that includes mp4 in the composition (no problems with comps with native AE elements). Apparently, it crashes at the point it comes to render the mp4 video.

Here is the solution that saved my file AEP and could render it in AE 25.1 (it might works for 25.0) :

- open brand new AE comp from scratch.

- Save it.

- throw your AE compromised file into it.

- walkthrough your compromised comp if it is ok, then Save it.

- at this point… you might be able to render… that worked for me.

i have tried all purges, all clear preferences, clean re-install… nothing de-bugged the file but this steps.

An other workaround, less usable, is to erase all mp4 sources from the library of the AEP and render it as quicktime .MOV RVB+ALPHA (it might work if it doesn't freeze before)…  but it means that your problematic MP4 is purely the background, and all the work to re-do after it…

hope it will works for the sake of community

[JasonsNickName]

I'm also having this same issue. I was in AE 25.1 on an M1 Max studio 64GB of ram. All i did was import an mp4 and it crashed a brand new project over and over. I'm going to try to roll back to version 24.6.4. Why is this happening Adobe? Don't release broken stuff.

[Warren Heaton]

@Capvel Martain 

The MP4 files do not need to be "erased" (deleted) from the project.  They can remain exactly as they are being used in each Composition.

While After Effects is closed, transcode the MP4 files to ProRes 422 LT or ProRes 422 HQ matching the settings of the MP4 files (frame size, frame rate, scan method).  RGB with alpha is not necessary when replacing MP4.  If there is limited storage space and the MP4 is low bitrate (35MBPs or lower), ProRes 422 Proxy is fine.

Before opening the After Effects project, take the MP4 files offline.  If the resulting ProRes transcodes have been checked thoroughly, it is okay to delete the MP4 files.

In the Project panel, use File > Replace Footage > File to replace the missing MP4 source footage with the corresponding ProRes footage. 

Then continue working in After Effects.

[Silvain Fuchs Pro]

Thank you. I saved my project in a AE24 compatible version and used AE24 withtout any problem. I'm surprised Adobe hasn't released a patch yet.

[Corey35286577mf8d]

I had this same issue, crashing and getting <RenderThreadExecutor> errors. After speaking with Adobe Support, the culprit seemed to be in Project Settings. When I had imported an old project, it seems that After Effects switched the renderer to "Mercury Software Only". 

In File > Project Settings I switched it back to "Mercury GPU Acceleration (Metal)" and everything worked again, no crashes, was able to render and save no problem.

[Warren Heaton]

@Corey35286577mf8d 

Thank you for sharing what resolved your issue.

[visionary_6650]

hi everyone , i am facing similar issue with Ae - 25.1.0 

it goes black all of a sudden when i press play the timeline or ever when i do camera tracking . it just frustrating. 

could someone tell me which version is stable and buggy free .\\

thanks 

Steps to reproduce:
    1. ...
 
Result: ...
Expected: ...
 
System info
    Application: After Effects v25.1.0.68
    OS: Windows v10.0.22631, RAM: 15.94 GB GB, CPUs (logical): 12

[catherine_4482]

Was having the same issue and have just tried switching to Mercury GPU Acceleration (Metal) and have been able to actually open a comp without the spinning beach ball of death!  Have not yet had a chance to give it a full test ( it being bed time) but this looks promising. 

[catherine_4482]

Well the switch to Mercury GPU seemed to work - for about 2 hours. Then, suddenly, it didn't. Back in the same non-functioning boat. So close to finishing this project I think I'm going to cry. Maybe downgrading the project will work. Fingers crossed.

[Xeneldix]

So far the only workaround I found is:

1. Restart AE width a new clean doc
2. Bring in the problematic AE file as an asset (import the AE file)
3. save (or overwrite problem file)
4. Now I can work and render
5. If happens again (surprise, has) repeat from step 1

[Ali-G-Coyote]

i have tried this and it crashes. 

My problem is that it doesn't render h264 but can render lossless. And when i convert it via AME, it gives the same damage file as AE.

[Double-D-Dean]

This tip saved me today. I was going crazy trying to work out why my project was crashing. Thanks!

[Capvel Martain]

Hi everyone !

My AE 25.2.0 (Build 131) didn't solve it and crashes the same way than 25.1 and 25.0, with "simple" comp, no thrid part effects whatsoever. It appears that AE and the Apple's M chips GPU has some conflicts when re-encoding à video (H264, ProRes422). As i said in previous post, native effects and vector animation have no issue. Freeze is only when video layer comes in the render (No issue during Edition the preview is always OK).

—>> Go to "Project parameters" (Cmd + Opt + shift + K) —> "Effect and render video"
and try the other GPU option. Then my render goes through 👍🏻

Issue appeard on my Macbook Pro M2Pro and Mac Studio M1Max, both on MacOs Sequoia 15.4