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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment