Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a1
Issue ID
UUM-120425
Regression
Yes
Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
How to reproduce:
1. Open the project “IN-113061_PhysicsMemoryUsage”
2. Open the SampleScene
3. Open the Profiler (Window → Analysis → Profiler)
4. Enter Play Mode
5. In the Hierarchy, select the “Spawner” GameObject
6. In the Inspector, click Spawn objects
7. Observe the Physics section in the Profiler
Expected result: The Physics Used Memory settles. In most cases settles at single digit MB numbers
Actual result: The Physics Used Memory keeps growing in steps. At first it grows rapidly, afterwards it takes some time to see the step up in memory growth
Reproducible with: 2023.3.0a5, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Not reproducible with: 2022.3.67f1, 2023.3.0a4
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: The “Spawner” GameObject spawns 1000 GameObjects that disable and enable their colliders. It has the option to also spawn GameObjects that destroy and re-add themselves to the scene
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
- Rigidbody2D.Slide correctly ignores colliders specified with "Physics2D.IgnoreCollision" however encountering them can still modify movement behaviour in subtle ways.
- [Quality Hackweek] A black separator appears when the left panel in the UI Builder tab is resized, and the tab is narrow
- Animator states quickly jump during the Blackboard navigation when the playing state is moved outside the view
- "New" Label overlaps long Asset names in Import Unity Package Window
Add comment