Search Issue Tracker
Fixed
Fixed in 2021.3.32f1, 2022.3.14f1, 2023.2.0b16, 2023.3.0a12, 2024.1.0a1
Votes
0
Found in
2022.3.8f1
2023.1.10f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-47478
Regression
No
An extra C# event is shown when creating two C# events on two temporary objects (each holding one event) using IL2CPP
Steps to reproduce:
1. Open the attached user project "MulticastDelegate.zip"
2. Make sure to change the path of the automatic memory snapshot ("Assets/Test.cs" line 83)
3. Build and run the Standalone Windows Player
4. Open Memory Profiler, select the taken snapshot and "Unity Objects"
5. Scroll down to the “MonoBehaviour“ script and select the “GameObject“ nested in it
6. On the right side under References expand “SceneRoot GameObject“-> “MonoBehaviour“
7. Finally expand the two “Test.HandPoser“ and observe the nested “System.Action<System.Boolean>“ events
Expected results: Two C# events are seen
Actual results: Three C# events are seen (See attached Repro.png)
Reproducible with: 2022.3.8f1, 2023.1.10f1, 2023.2.0b7, 2023.3.0a3
Could not test on 2021.3.30f1 due to Memory Profiler Capture not being available
Reproducible on: Windows 10 2H22
Not reproducible on: No other environment tested
Notes:
-Not reproducible with Mono Scripting Backend
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Tilemap Collider 2D is not updating the Collider shapes when removing Tiles on the Tilemap component
- Inspector with the scrollbar is unusable when Material properties are edited and the scene is saved
- The Rendering Profiler module statistics are zero when Application.targetFrameRate is set
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
Add comment