Search Issue Tracker
Fixed in 5.6.0
Votes
2
Found in
5.5.0f3
Issue ID
857443
Regression
No
[GC Alloc]Playables API "SetInputWeights()" method generates tons of garbage collector allocation
Steps to reproduce:
1. Download and open the attached project.
2. Open the Profiler window
3. Enter play mode
Expected result: no, or minimal GC Alloc
Actual result: SetInputWeight generates a lot of garbage collector allocation
Reproduced on: 5.3.7p2, 5.4.4f1, 5.5.0f3, 5.5.0p3
Unable to test on 5.6 because the Playables API seems to not work
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
PhilSA
Jan 19, 2017 15:46
I tested it in 5.6b4 after these examples were posted : https://forum.unity3d.com/threads/animationclipplayable.451854/#post-2926897
The GC alloc for SetInputWeight() seems to be gone completely now. The problem appears to be fixed
TheValar
Jan 13, 2017 18:34
This is a huge problem. I think many use-cases for this system involve setting input weights every frame. For me this is basically unusable until this is fixed :(