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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment