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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment