Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-120146
Regression
No
Crash with multiple stack traces when increasing the Terrain Detail Instance count past a certain threshold
How to reproduce:
1. Open the attached “IN-110483.zip” project
2. Open the “SampleScene”
3. In the Hierarchy window, select the “Terrain” GameObject
4. Under Terrain Settings, increase the “Detail Resolution Per Patch” value from 16 to 128
5. Observe the crash
Reproducible in: 2023.1.0a1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of stacktrace:
{noformat}0x00007FF93555D94B (Unity) MemoryProfiler::GetAllocationRoot
0x00007FF9359B176C (Unity) MemoryProfiler::UnregisterAllocation
0x00007FF935563CF4 (Unity) MemoryManager::RegisterDeallocation
0x00007FF935565E42 (Unity) MemoryManager::TryDeallocateWithLabel{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
- Project Auditor suggests to update package to a lower version than installed when the recommended package version is not the latest version
- Low performance when multiple meshes using BlendShape are rendered on screen
- TMP Dropdown visually corrupts or disappears when its own GameObject is assigned to "Caption Image" or "Placeholder" elements
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
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 (6000.5.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.