Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
Issue ID
UUM-113041
Regression
No
Crash on ConcurrentCache when opening a specific project
How to reproduce:
1. Open the attached “CrashRepro“ project
Reproducible with: 6000.0.54f1, 6000.1.13f1, 6000.2.0b11
Not reproducible with: 6000.3.0a3
Fixed in: 6000.3.0a1
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
First few lines of the stack trace:
#0 0x000001075467b6 in ConcurrentCache<TypeTreeCache::CacheKey, TypeTreeCache::CachedTypeTreeData, TypeTreeCache::HashGenerator, std::__1::equal_toTypeTreeCache::CacheKey>::Find(TypeTreeCache::CacheKey const&, TypeTreeCache::CachedTypeTreeData)
#1 0x0000010754601f in TypeTreeCache::GetTypeTree(Object const*, TransferInstructionFlags, TypeTree&)
#2 0x00000107528788 in SerializedFile::SerializedType::CompareAgainstNewType(Object const&, core::vector<SerializedFile::SerializedType, core::allocator<SerializedFile::SerializedType, 0ul>> const&, TransferInstructionFlags) const
#3 0x0000010753424a in SerializedFile::ReadObject(long long, ObjectCreationMode, bool, TypeTree const*, bool, Object&, CacheReaderBase*) const
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
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.