[jay_kyburz]

Only in Debug builds. If you rely on it in a release build you will crash.

https://github.com/godotengine/godot-proposals/issues/1589 https://github.com/godotengine/godot/issues/41179

Reduz doesn't want the fix in release builds because the will be slower!

[nightowl_games]

I don't understand. That's not what that PR says. That PR is about using == null. It offers no substantial information about is_instance_valid.

[jay_kyburz]

Apologies, you might need to do some digging and research on your own.

On Oct 2 @RandomShaper said "is_instance_valid() was made thread-safe, but it's still not something you can trust. An object allocated at the same address as a freed one will report a false positive. That's, of course, considering that what you want to check is that your variable is still pointing to the object you assigned, and not to just some object, which I think is the case.

@reduz respoinded with "Ah that may be still the case of 3.2, but in 4.0 this function is 100% trustworthy"