Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
2022.3.17f1
Issue ID
UUM-59884
Regression
No
Crash on BucketAllocator::Allocate when opening a project after a failed build
Reproduction steps:
1. Open the attached project “ReproProj”
Expected result: The project is opened
Actual result: The Editor crashes
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.1.20f1
Not reproducible with: 2023.2.0a1, 2023.2.4f1, 2023.3.0b1
Reproducible on: macOS 14.2.1 (M1 Max), Windows 10
Not reproducible on: No other environment tested
First few lines of the stack trace:
{{#0 0x00000100cea5dc in BucketAllocator::Allocate(unsigned long, int)}}
{{#1 0x00000100cddc34 in DualThreadAllocator<DynamicHeapAllocator>::Allocate(unsigned long, int)}}
{{#2 0x00000100cd1c28 in MemoryManager::Allocate(unsigned long, unsigned long, MemLabelId const&, AllocateOptions, char const, int)}}
{{#3 0x00000100cd1320 in malloc_internal(unsigned long, unsigned long, MemLabelId const&, AllocateOptions, char const, int)}}
{{#4 0x00000100d015c0 in dynamic_array<int, 0ul>::dynamic_array(unsigned long, MemLabelId const&)}}
{{#5 0x00000101507870 in TypeTreeShareableData::TypeTreeShareableData(MemLabelId const&)}}
{{#6 0x000001014fe108 in TypeTree::TypeTree(MemLabelId 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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.