Search Issue Tracker
Fixed in 2022.3.36f1
Fixed in 2022.3.X, 6000.0.X, 7000.0.0a1, future release
Votes
0
Found in
2022.3.32f1
6000.0.5f1
Issue ID
UUM-73491
Regression
Yes
Crash on free_alloc_internal when clearing Shader variants in certain projects
How to reproduce:
1. Open the attached "ShaderCrashRepro" project
2. Open Project Settings… > Graphics
3. Press Save to asset
4. Save and replace the existing Shader variants
5. Press Clear
Reproducible with: 2022.3.28f1, 2022.3.32f1, 6000.0.5f1
Not reproducible with: 2021.3.39f1, 2022.3.27f1
Reproducible on: macOS 14.5 Sonoma (Intel), Windows 11 (reported by user)
Not reproducible on: No other environment tested
First few lines of stack trace:
0x00007ff62b71de1a (Unity) free_alloc_internal
0x00007ff62aff9f91 (Unity) core::vector<void * __ptr64 [38],0>::~vector<void * __ptr64 [38],0>
0x00007ff62bbd0fe7 (Unity) std::_Tree_val<std::_Tree_simple_types<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo> > >::_Erase_tree<std::allocator<std::_Tree_node<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo>,void * __ptr64> > >
0x00007ff62bbd0fcf (Unity) std::_Tree_val<std::_Tree_simple_types<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo> > >::_Erase_tree<std::allocator<std::_Tree_node<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo>,void * __ptr64> > >
0x00007ff62bbd0fcf (Unity) std::_Tree_val<std::_Tree_simple_types<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo> > >::_Erase_tree<std::allocator<std::_Tree_node<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo>,void * __ptr64> > >
0x00007ff62bbd0fcf (Unity) std::_Tree_val<std::_Tree_simple_types<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo> > >::_Erase_tree<std::allocator<std::_Tree_node<std::pair<PPtr<Shader> const ,ShaderVariantCollection::ShaderInfo>,void * __ptr64> > >
0x00007ff62bbd557d (Unity) ShaderVariantCollection::ClearVariants
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment