Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.2.0f3
Issue ID
969832
Regression
No
HashSet.TrimExcess causes an increase in memory
Steps to reproduce:
1. Open attached project
2. Open "Test" Scene
3. Enter Play mode
4. Select "TrimExcess-3.5" in the hierarchy
5. Toggle Disable/Enable checkmark for TestHashSetTrimExcessBug Script component
Expected result: the function trims the HashSet to the minimum size required to contain it.
Actual result: the HashSet increases in size each time TrimExcess is called on it.
Reproduced with: 5.6.1f1, 5.6.1f1, 2017.3.1f1, 2017.3.1f1, 2018.2.0a1
Note: the issue does not appear when using .NET 4.6. It can be tested by enabling "TrimExcess-4.6" game object in the hierarchy and repeating step #5 with it.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment