Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.37f1
2022.3.31f1
6000.0.4f1
Issue ID
UUM-72829
Regression
No
Crash on UnityMain while in Player when mesh.vertexBufferTarget and mesh.indexBufferTarget is set in a specific order
Reproduction steps:
1. Open the attached “repro-IN-76657“ project
2. Build the project with “Scenes/SampleScene” added in the “Scenes In Build“ list
3. After the build finishes, open the “repro_IN-76657/Build“ folder and run the “UnityCrashMay24“ executable
4. Observe the crash
Reproducible with: 2021.3.39f1, 2022.3.31f1, 6000.0.4f1
Reproducible on: Windows 11 (10.0.22631) (user’s), Windows 10 (22H2)
Not reproducible on: No other environments tested
Notes:
* Crash is only reproducible in Player and not in the Editor
* Reproducible after deleting the Library folder before building
* Unity Bug Reporter window doesn’t appear after the crash
First few lines of the stack trace:
0x00007FFD9C4C926E (UnityPlayer) UnityMain
0x00007FFD9BC55E96 (UnityPlayer) UnityMain
0x00007FFD9BC545D0 (UnityPlayer) UnityMain
0x00007FFE38E37344 (KERNEL32) BaseThreadInitThunk
0x00007FFE3A2C26B1 (ntdll) RtlUserThreadStart
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
- Crash on Object::GetCachedScriptingObject when entering Play Mode
Add comment