Suppressing the new AE Crash Options after an unregular application exit.

Maris

@jeff Hey Jeff, thanks for getting back.

Arie has already upvoted my Adobe Forum Post so i figured you were taking a look at things.
We are rebooting our machines every night because we have experienced issues with AE instances that ran for a long time.

I think the crashes are cause by either the tasked reboot force quitting AE or by the fact that we have three instances of Templater Bot running the same project at once and the way that AE checks for chashes is some kind of quit statement in the projectfile itself.

Because once one project is opened, we get the Crash Options dialogue on instance 2 and 3 (run with the -m parameter).

Instance 2 and 3 generate on demand previews that are shown to the creators in our frontend. We are running two instances to speed up the polling of our json data (still limited to 0.2 min) to have a result asap.

I guess the issue is with having the same project open multiple times.

I could fork a “preview project” but i really dont want to do that everytime there are updates to the template.

I just want adobe to not fk with my day

At the moment i’m thinking of going back to 23.1 or 23.0 and just disabling updates.

Jeff

@maris

We’re currently working to see if there’s a way around this, but I did have a few suggestions that might be helpful in the meantime.

First, I think it would be helpful if we could figure out whether the Crash Repair Options dialogue is being caused by all three instances of Templater accessing the same project or whether it’s just a flag that is set when the AE instances are closed abruptly.

In your last message, you stated that once one project is opened, the other two instances immediately throw the Crash Repair Options dialogue. This doesn’t seem to be in line with the way that we’re seeing that flag operate, so I think it would be helpful if we could try booting up each instance of Templater in a slightly different order to confirm that the issue doesn’t occur unless the same file is accessed simultaneously.

If that’s the case, it might be useful to set the second and third instances of Templater to load up with a “dummy” project and then use the aep reserved column to switch them over to the main project file. This would allow us to boot the system up in a way that avoided accessing the same project simultaneously.

Another option that we might consider would be the use of a rudimentary Event Script to exit After Effects gracefully at the end of each day.

This is extremely basic, but I did some testing today with this script:

var exitFlag = $D.job.get("exit");
if (exitFlag === "y") {
	app.project.close(CloseOptions.DO_NOT_SAVE_CHANGES);
	app.quit();}

and got some excellent results. I registered this script to the “After creating output” event under “Output Processing”. It checks for a value in the Data Source named “exit” (with no quotes) and then closes After Effects if that flag is set to “y” (also with no quotes).

Using this method or something similar might allow us to close out Templater gracefully with a specific Job added at the end of each day when the reboot is set to occur. This might get us around the Crash Repair Options dialogue when the system is booted back up.

We’ll keep looking for better ways to get around this issue on this side, but I thought I’d throw this information out there in case it was worthwhile.

Thanks,

Jeff

Maris

@jeff

Well… i didnt know THAT existed.

Jon

@maris What is wild is that I looked through every option in the console, but somehow overlooked that one. That is very helpful to know.

Jon

@Maris adding for future reference, since the Adobe forum link appears to be dead, and don’t want the info lost to history.

There is a hidden developer Console panel that is accessible by hitting ctrl + f12. From there you can open the menu on the panel and navigate to Debug Database View. In that view, you can search for the option AEDebugShowPreviousCrashWarning. By default it will be checked/true, but you should be able to disable it by unchecking that option.

Tom10

@Jon I been using this successfully in 2023 versions of AE, but recently noticed it is… Missing in 2025? Have you noticed this, or I am just not lucky? ha!

Jeff

@Tom10

We did some testing this morning, and it appears that the AEDebugShowPreviousCrashWarning key has been removed from AE 25.0.1 and AE 25.1.0. One of our engineers reported that it was still present in 25.0.0, but it seems like Adobe is removing this as a debug option moving forward.

This would explain why the forum posts that were previously linked in this thread seem to have been deleted from Adobe’s site.

It’s possible that you might be able to add the debug string:

AE.DebugShowPreviousCrashWarning true true

back to the Debug Database.txt file manually, but even if it works (which is unclear at the moment), I doubt that it will be a stable solution in the long run.

At this point, I think the only option to get this option restored would be to contact Adobe directly and see if they’d be willing to consider adding the feature in a later update.

Unfortunately, that’s all we know at the moment, but if we get any updates or have any other input on this, we’ll definitely update this thread.

Thanks,

Jeff

Tom10

@Jeff thats a great suggestion! Tried it (IMO it should be false false, as first boolean reflects the value in written, where second the checkbox itself)

To force this to troubleshoot, killing AE should be done while intro dialog is shown. Unfortunately that did not do the trick.

BTW a lot of options are dismissed from 25.1 compared to 23.6. No response from Adobe support. Will update if found anything new.

Tom10

From Adobe support:

“Had shared the case with my seniors. The Console was a developer tool and was there till Version 2024 and have been discontinued for now.”

tschoel

@Tom10 @Jeff @Maris @Jon
Had the same issue for our own custom renderfarm. When starting AE over cmd you can actually add a “-noerr” flag that suppresses this popup.

So now we always start AE over a .bat file with this flag:
start afterFX.exe -noerr