Search Issue Tracker
In Progress
Fix In Review for 6000.0.57f1, 6000.1.X, 6000.2.3f1
Under Consideration for 6000.3.X
Votes
0
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
Issue ID
UUM-112248
Regression
Yes
Memory usage increases each time the MeshCollider Component is turned off and on
How to reproduce:
1. Open the “IN-109119.zip“
2. Open the “SampleScene“
3. Open the Task Manager
4. Enter Play Mode
5. Observe the Task Manager
Expected result: Memory usage is stable and does not increase
Actual result: Memory usage increases fairly fast ( 200MB/min )
Reproducible in: 2023.3.0a5, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Not reproducible in: 2023.3.0a4
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Leaving Play Mode releases the memory
- The more GameObjects there are with the same “EnableSwitch“ script, the faster the memory builds up
- The MeshColliders do not have to be disabled/enabled in the same frame
- Reproducible in the Player as well
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection problems when unbaked Reflection Probes are present
- Light Explorer columns sorting arrow is too small
- Context menu actions (Collapse All, Expand All, Enable All, Disable All, Remove All, Reset All) do nothing in Volume component
- [Android] Audio volume decreases when returning to the app during screen recording
- Graphical issues are caused by GPU Occlusion Culling when using Amplify Shaders
Add comment