Community Manager

Question

Force Quits during After Effects Launch

Forum|Forum|1 year ago
January 16, 2025
5 replies
580 views

Greetings After Effects Beta users — Paul here from the AE Quality Engineering Team.

We have a bit of a mystery with AE that I'm hoping to get some insight around.

Within our crash reporting system we see a significant number of force quits occuring in AE during or just after launch. For most of these, we do not see anything having occurred previously that would have required the user to force quit. We don't see a hang or any error having happend. Everything looks fine.

We are concerned there is a problem or failure that we're missing here.

Now, a question and a request:

1. How frequently are you force-quitting (Mac) / terminating (Win) AE during or just after startup for reasons other than a hang or other problem occuring with AE. Could be for any reason other than something wrong with AE that required you to force-quit it

2. If you do encounter an issue requiring a force quit or termination, could you please make a short reply to this post indicating what happned with AE that made it necessary for you to terminate it?

We would really appreciate any help with this.

Paul Uu

Adept_thinker6C2A

Participating Frequently

1. This happens occasionally when I open the wrong version of AE, but most of my force quits are for AE hangs during loading.

2. I'm experiencing this hang issue seemingly 50% of the time I try to open a project. Doesn't seem to be project specific. Always gets stuck on loading screen and turns into spinning ball of death (Mac). This has been happening for the past few months on the latest versions - even after updating to the latest (non-beta) builds.

Only happens on initial open, meaning that once I've done a force quit and relaunch the same exact project, AE opens without issue and as expected.

Feel free to reach out to me for additional info and troubleshooting.

Thanks for looking into this, AE team!

G

gabgren1

Participant

hey. plugin dev here. another dev suggested that maybe what you see is us stopping our debuggers with the ae process attached while developing plugins and testing them on beta?

J

jonah.c.l

Inspiring

Yep this is typical behaviour while I'm developing plugins too. It's faster to force quit than quit properly, which adds up when I'm restarting AE ~30 times/hr. Also I don't only develop on Beta, so you'd see this on 2023-2025 from devs like me.

At least with the way I develop, the telltale sign it's from developing is that I'll force quit many times per hour, but not every time I open AE. And most of the times I leave it open to use it, it's not for more than 2-3 minutes.

Z

Zachary Antell

Participant

99% of the time its because I accidentally clicked it

L

lucasvasconcelos

Participating Frequently

I have a problem with both the regular version 25 and the beta version 25. When importing a video file, I can use After for a few minutes and it simply crashes. I press command + s to save and it gets stuck at 99% and won't get out of it. I need to force close it and open it again. This didn't happen in After 24.

sskaz

Inspiring

For me, sometimes I accidentally opened the wrong version. Currently, I have 2024, 2025, and the occassional beta installed and sometimes it’s a guessing game which version will launch when I open an aep.

RobBarrett

Community Expert

This happens a lot for me too – I have various versions in my dock, and sometimes I'll click on the wrong one, and don't want to wait to close it properly.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded