Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2021.3.42f1
2022.3.43f1
Issue ID
UUM-78782
Regression
No
Crash on MemoryProfiler::UnregisterAllocation when opening a specific scene
Reproduction steps:
1. Open the attached project "CrashRepro"
Expected result: Project opens
Actual result: Editor crashes
Reproducible with: 2021.3.42f1, 2022.3.43f1, 2023.1.20f1
Not reproducible with: 2023.2.0a1, 6000.0.16f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}Obtained 55 stack frames
0x00007ff6befaa41c (Unity) MemoryProfiler::UnregisterAllocation
0x00007ff6bebe8cf3 (Unity) MemoryManager::Deallocate
0x00007ff6bebe6a1b (Unity) operator delete
0x00007ff6bf04b369 (Unity) std::vector<std::pair<std::pair<unsigned short,unsigned short>,float>,std::allocator<std::pair<std::pair<unsigned short,unsigned short>,float> > >::_Emplace_reallocate<std::pair<std::pair<unsigned short,unsigned short>,float> >
0x00007ff6bf04f8af (Unity) vector_map<ShaderTagID,ShaderTagID,std::less<ShaderTagID>,std::allocator<std::pair<ShaderTagID,ShaderTagID> > >::operator[]
0x00007ff6bf05d52b (Unity) Material::SetOverrideTag{noformat}
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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.