-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Crash when opening project with glb mesh with external meshes #84026
Comments
Already broken in |
Unfortunately it seems the the external mesh files generated by beta 3 are corrupt and will stay corrupt. Just wasted a bunch of time bisecting |
Closing this one since it's redundant with the already linked and reported issues. I wasn't able to narrow down the commit where this happened. I think someone that understands better how importers work perhaps could help on this. I think my test were not "clean enough" to pinpiont where this bug was introduced. I tried going back to 4.1 and generating a mesh with it and opening it with 4.2 but it works fine. I'll go to bed and hand this over. |
Well this one has a MRP and a better defined scope, so it seems useful to me as the main bug report to debug the issue. |
Tested on current master at 09946f7 with ASAN and I can see the crash. Running a non-ASAN build gives different crash locations as often happens with heap corruption. A heap buffer overflow happens here when writing to godot/scene/resources/mesh.cpp Line 1109 in 09946f7
In the loop Full stack trace:
|
Godot version
v4.2.beta.custom_build [09946f7]
System information
Fedora, RX 590
Issue description
I was using my VFX project and I am not able to use any mesh imported from a glb file. Godot hangs and crashes in different ways in my project. Sometimes with
double free or corruption (out)
sometimes withfree(): invalid next size (normal)
mrp crashes with
Debug build output:
NOTE: I tried to clear the .godot folder. Issue persists.
Steps to reproduce
Open mrp
Minimal reproduction project
mesh-crash.zip
The text was updated successfully, but these errors were encountered: