Search Issue Tracker
In Progress
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X
Fix In Review for 6000.4.X
Votes
2
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment