Search Issue Tracker
Active
Votes
1
Found in
1.9.3
Issue ID
UUM-128749
Regression
No
Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Kickball.unity” Scene
3. Enter Play Mode
4. Exit Play Mode
5. In menu bar click “Tools > Reload Tools”
6. In the Reload Tools window click “Reload Domain“
7. Observe the Console
Expected result: No persistent memory leaks exists
Actual result: Message “Leak Detected : Persistent allocates 1 individual allocations“ is present
Reproducible with: 6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.0a3 (05fffdb25ae2)
Not reproducible with: 6000.4.0a5
Fixed in: 6000.5.0a1 (0136d7329743)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- With 6000.4.0a3 and 6000.4.0a4 only sometimes reproducible
- The enabling logic is located in GoInGameServerSystem.cs, where GhostDistanceData singleton and GhostImportance component are added
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment