Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.2.0f3
Issue ID
985459
Regression
No
Vector3Int causes boxing and high memory allocation when used as key in dictionary
Reproduction steps:
1. Download "BetterVector3Int.zip" project and open in Unity
2. Select Window > Profiler > Memory
3. Select Testscripts in hierarchy
4. Disable script "Test My Vector 3 Int"
5. Enter Play mode
Expected: total memory should stay around 100 MB
Actual: total memory usage grows from about 220MB to 0.75GB
Reproduced: 2017.2.0a4; 2017.2.1p2; 2017.3.0p2; 2018.1.0b3; 2018.2.0a1
Note: 2017.1-2017.2.0a3 does not have Vector3Int
Fixed on: 2018.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Add comment