Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.3.3f1
2019.1.0a11
2019.1.0a12
2019.2.0a1
Issue ID
1114295
Regression
Yes
UnitySynchronizationContext.ExecuteTasks() causes per frame GC Alloc
Steps to reproduce:
1. Download 1114295_repro.zip and open "Scene" scene
2. Open Profiler window
3. Enter play mode
4. Search for UnitySynchronizationContext.ExecuteTasks()
Expected results: observe UnitySynchronizationContext.ExecuteTasks() causes 56 bytes per frame GC Alloc.
Actual results: no GC allocation from UnitySynchronizationContext.ExecuteTasks()
Reproduced with: 2019.2.0a2, 2019.1.0a14, 2018.3.3f1
Not reproducible with: 2018.3.2f1, 2019.1.0a10, 2017.4.19f1
Regression introduced in: 2018.3.3f1, 2019.1.0a11
Comments (1)
-
stonstad
Apr 23, 2020 18:36
I am seeing 392B every N frames in an empty scene with one camera in 2019.3.9f1. Image: https://i.imgur.com/X68ARd2.png
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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
- Search Default option for Column Format does not reset the column's format
Resolution Note (fix version 2019.2):
Fixed in: 2019.2.0a4, 2019.1.0b2