Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-132365
Regression
No
"DebugAllocatorMode" option changes when changed in another Editor instance
Reproduction steps:
1. Create a new project
2. Open Diagnostics (Edit > Preferences > Diagnostics)
3. Under “Core” change “DebugAllocatorMode” to “DecommitMemory“
4. Close project
5. Create a new project and open with 2023.2.22f1
6. Repeat step 2
7. Under Core change “DebugAllocatorMode” to “ReleaseMemory”
8. Repeat step 4
9. Open previous project
10. Repeat step 2
11. Observe the “DebugAllocatorMode” option
Expected result: “DebugAllocatorMode” is set to “DecommitMemory“
Actual result: “DebugAllocatorMode” changed to “ReleaseMemory“
Reproducible with: 6000.0.65f1, 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Testing environment: Windows 10 Enterprise 21H2
Note:
- When first opening with 2022.2.22f1 and then with 6000.3.2f1, instead of Core UNITY_MODULE_NAME is present
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment