Search Issue Tracker
Fixed in 2022.3.7f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a1
Votes
0
Found in
2022.3.5f1
2023.1.4f1
2023.2.0a23
2023.3.0a1
Issue ID
UUM-42428
Regression
Yes
Memory allocator crash when opening a project
Reproduction steps:
1. Download and extract the attached “repro-project“
2. Open the project
3. Observe the crash
Reproducible with: 2022.2.0a12, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Not reproducible with: 2021.3.28f1, 2022.2.0a11
Reproduced on: Windows 10 Pro
First few lines of the stack trace:
{{0x00007FF7149E8EB6 (Unity) baselib::UnityClassic::detail::chunked_allocator<ThreadsafeLinearAllocator<1>::LocalLowLevelAllocatorProxy,5,1024,8>::chunked_allocator<ThreadsafeLinearAllocator<1>::LocalLowLevelAllocatorProxy,5,1024,8><LowLevelVirtualAllocator * __ptr64 & __ptr64,unsigned short & __ptr64> }}
{{0x00007FF7149E96B3 (Unity) ThreadsafeLinearAllocator<0>::ThreadsafeLinearAllocator<0> }}
{{0x00007FF7149D8042 (Unity) MemoryManager::InitializeDefaultAllocators }}
{{0x00007FF7149D97D6 (Unity) MemoryManager::LateStaticInitialize }}
{{0x00007FF715D1502E (Unity) Application::InitializeProject}}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
Add comment