Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.68f1
6000.3.11f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-137242
Regression
No
User Reporting package allocates per-frame coroutine (GC Alloc) even when MetricsGatheringMode is Disabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Open Profiler
5. Enable Deep Profiling
6. Search for “UserReportingClient“
7. Wait a few seconds
8. Select a frame in Profiler
9. Observe
Expected result: “UserReportingClient.Update()”, “UserReportingClient.SampleClientMetric()“ and UserReportingSceneHelper.UpdateClientByFrame() [Coroutine: MoveNext] has GC Alloc of 0 B
Actual result: “UserReportingClient.Update()” and “UserReportingClient.SampleClientMetric()“ are present with the GC Alloc of 80-120 B
Reproducible with: 6000.0.68f1, 6000.3.11f1, 6000.4.0f1, 6000.5.0a7
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- note that UserReportingSceneHelper.UpdateClientByFrame() [Coroutine: MoveNext] is also running every frame
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment