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
-
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
- Basic UI Toolkit panels do not render when using URP+RenderGraph+D3D12
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
Resolution Note (fix version 2019.2):
Fixed in: 2019.2.0a4, 2019.1.0b2