Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X, 2018.1.X
Votes
0
Found in
2017.1.2p2
Issue ID
967201
Regression
No
Unity generates garbage when UnityEvents are invoked with value type parameters if the event has a static event handler
To reproduce:
1. Open the included project "UnityEventsBoxing2_UnityProject".
2. Open the Unity profiler and instruct it to record.
3. Open and play the scene "TestScene-NoGCAlloc". The UI text explains how the test is set up. Observe the profiler memory view and notice that no garbage is generated when the event fires in this case because it only has a dynamic event handler. This is good!
4. Open and play the scene "TestScene-GCAlloc". The UI text explains how the test is set up. Observe the profiler memory view and notice that 20 bytes of garbage are generated each time the event fires because it has a static event handler. This is bad...
Reproduced in 2017.1.2p2, 2018.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Add comment