Search Issue Tracker
Active
Under Consideration for 6000.5.X, 6000.6.X
Votes
1
Found in
6000.5.0a1
6000.6.0a1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment