Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b4, 2023.3.0a1, 2024.1.0a1
Votes
0
Found in
2021.3.25f1
2022.2.20f1
2023.1.0b17
2023.2.0a16
2024.1.0a1
Issue ID
UUM-36663
Regression
Yes
Crash on SubProgramBlobWriter::Flush when building a project
Reproduction steps:
1. Open the attached “repro-project“
2. Build And Run
3. Observe the crash
Reproducible with: 2021.3.12f1, 2021.3.25f1, 2022.2.20f1, 2023.1.0b17, 2023.2.0a16
Not reproducible with: 2020.3.48f1, 2021.3.11f1
Reproduced on: Windows 10 Pro, macOS 13.3.1 (Intel) (by reporter)
First few lines of the stack trace:
{{0x00007FF79A6E6247 (Unity) SubProgramBlobWriter::Flush }}
{{0x00007FF79A6D7848 (Unity) CompileShaderSubprograms }}
{{0x00007FF79B192881 (Unity) Shader::Transfer<StreamedBinaryWrite> }}
{{0x00007FF799AFBD7B (Unity) SerializedFile::WriteObject }}
{{0x00007FF799AE577B (Unity) PersistentManager::WriteFile}}
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a1):
Previous versions of Unity allowed a value of 0 for the default shader chunk size to be stored with player settings. This caused problems during allocation size computations. This value is no longer allowed, and the Editor now prevents a 0 value from being used or stored.