Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a1
2018.1.0a3
Issue ID
967231
Regression
Yes
MaterialPropertyBlock calls GC.Alloc when using MaterialPropertyBlock.GetVector or MaterialPropertyBlock.SetVector
Reproduction steps:
1. Open project attached (repro.zip).
2. Open scene "Scene".
3. Open Profiler.
4. Press Play.
Expected result: GC.Alloc will not allocate memory each frame.
Actual result: GC.Alloc is allocating memory. In addition, it seems that performance of NewBehaviourScript.Update() is about 10-15% slower than before.
Reproduced on: 2018.1.0a1, 2018.1.0a2
Works fine on: 2017.3.0b8
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