godotengine / godotengine/godot
Certain GLB or GLTF file crashes the editor during import
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
- Reproducible in 32 bit Godot v4.2.1.stable.official [b09f793f5]
- Not reproducible in 64 bit Godot v4.2.1.stable.official [b09f793f5] and 32 bit Godot v3.5.3.stable.official [6c814135b]
### System information
Godot v4.2.1.stable - Windows 10.0.22621 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1650 (NVIDIA; 31.0.15.3667) - AMD Ryzen 5 4600H with Radeon Graphics (12 Threads)
### Issue description
Importing certain GLB or GLTF file results in the editor crashing during importing progress. Opening it back up will restart the importing progress and crashing the editor again. Certain GLB or GLTF file works just fine. After testing, this issue only occurs in the 32 bit version of Godot v4.2.1-stable, it works normally in 32 bit version of Godot v3.5.3-stable. There was nothing logged during the crash while using the verbose console.
Working
https://github.com/godotengine/godot/assets/32596839/e69ee40e-2e22-4cf2-ad00-23ac07c8a111
Crashing
https://github.com/godotengine/godot/assets/32596839/a8adbc21-6157-4534-9cc5-a61565c5de68
### Steps to reproduce
1. Create a Godot project using the compability setting
2. Drag and drop a GLB file into the FileSystem
3. If it is the Barbarian.glb, it will crash. If it is the arrow_green.gltf.glb, it will import normally.
### Minimal reproduction project (MRP)
[Issue Test.zip](https://github.com/godotengine/godot/files/13975899/Issue.Test.zip)
Contributor guide
Research direction
Start with the linked minimal reproduction project and reproduce the crash by importing Barbarian.glb in 32-bit Godot v4.2.1 using the Compatibility setting. Compare it with arrow_green.gltf.glb and the 64-bit or Godot 3.5.3 results; done means the affected GLB/GLTF imports without crashing the editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100