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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment