Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Threading errors when threading is not used. #99660

Closed
BastiaanOlij opened this issue Nov 25, 2024 · 3 comments
Closed

Threading errors when threading is not used. #99660

BastiaanOlij opened this issue Nov 25, 2024 · 3 comments

Comments

@BastiaanOlij
Copy link
Contributor

Tested versions

  • Not reproducable in Godot 4.3 stable
  • Reproducable in Godot 4.4 master (9e60984)

System information

Windows 11 - Forward+ - NVidea 4070Ti

Issue description

Opening an existing project that has been working since Godot 3 days in latest master floods the log with Moving child node positions inside the SceneTree is only allowed from the main thread. Use call_deferred("move_child",child,index).

Image

Note that these errors are given just opening this scene in the editor. To my knowledge the only place threading is used in this project is that its using the ResourceLoader but this only effects runtime.

Note that at the same time the console within VSCode gets flooded with:
Image

The error not referring to what code leads to this issue means we're looking for a needle in a haystack and with the editor becoming unresponsive, it's a challenge.

My best guess is that this is caused by this project using @tool scripts that hook into the changed signal of a 3D curve which both triggers the CSG polygon that build the track updating, as well as reposition various other elements.

Steps to reproduce

As right now it's impossible to pinpoint the cause of this, the only way to reproduce is to open the effected project.

Minimal reproduction project (MRP)

BastiaanOlij/vehicle-demo#15

@BastiaanOlij
Copy link
Contributor Author

Well, I'm stumped. After going through a full bisect, the problem has just disappeared. I'm at a loss to explain it.. Even resetting the project back to freshly cloned from GIT..

@theraot
Copy link
Contributor

theraot commented Nov 25, 2024

Perhaps related to Godot rebuilding cache, or changes in internal formats from one version to another?

@BastiaanOlij
Copy link
Contributor Author

Perhaps related to Godot rebuilding cache, or changes in internal formats from one version to another?

Definitely a possibility, this project has lots of generated geometry that may have been stored in an old format and failed to update nicely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Unassessed
Development

No branches or pull requests

2 participants