Random ‘Found the key outside the animation range’ errors causing crashes in exported build

[jitdev87]

Tested versions

The build was exported with Godot 4.4.1.stable.
The game uses Forward+ with Vulkan by default.

System information

Windows 10/11 - Godot 4.4.1.stable - Vulkan (Forward+)

Issue description

I’m getting random reports of crashes to desktop in the exported build of my game. I can’t reproduce the issue locally, but the logs from affected users consistently include the following:

ERROR: Found the key outside the animation range. Consider using the clean-up option in AnimationTrackEditor to fix it.
at: _find (scene\resources\animation.cpp:2445)

My game isn’t the only one affected — for example, players of Road to Vostok have reported similar crashes. The developer mentioned that they investigated it and suspect it’s a Godot engine bug:
https://steamcommunity.com/app/1963610/discussions/0/4633734719581728460/

I’ve searched through related issues here, but many of them seem to get closed without being properly addressed.

Some devs have mentioned fixing it by adjusting the keyframe where they play an audio clip in the affected animation. However, in my case, I’m not even using audio clips in animations, and users still encounter this crash.

Has anyone else run into this issue? Any known solutions?

Steps to reproduce

Not reproducible locally; the issue appears to happen only in exported builds for some users.

Minimal reproduction project (MRP)

[QbieShay]

Please try to isolate the problem and make a minimum reproduction project - without it it's going to be really hard to fix the issue

[precup]

Looking at the logs you've linked from Road to Vostok shows that a lot of work happens after that error is printed, it's not causing a crash for them and there are renderer errors printed significantly later that seem more relevant.

It could still be the same issue, but symptoms don't line up well.

[jitdev87]

Looking at the logs you've linked from Road to Vostok shows that a lot of work happens after that error is printed, it's not causing a crash for them and there are renderer errors printed significantly later that seem more relevant.

It could still be the same issue, but symptoms don't line up well.

Could be unrelated, but if it's showing up in the log as an error, something has to be wrong, right?
I'm having the same problem with my players, they're experiencing seemingly random crashes to desktop, and that error is the only suspicious thing in their logs.

[TokageItLab]

It sounds that related with #106654 (comment). Please check if the PR fix this issue.