Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4.0f1
2018.3.14f1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1156836
Regression
No
Profiler Timeline fails to display one of workers Job information when Job execution takes more than 6 Frames
How to reproduce:
1. Open "case_1156836.zip" project
2. In Project Window select SampleScene
3. In Hierarchy Window select "Example" GameObject > put a tick on Example (Script) Component
4. Play the Scene
5. When " Done" appears in Console Window - Pause the Scene
6. Open Profiler Window and put the marker in Profiler on the Frame which was logged out in Console
7. Extend Job section in Profilers Timeline > go further with one Frame (as in attached "Further Frame.png")
Expected result: All Workers Jobs are shown in the Timeline
Actual result: Worker that takes 6 or more physics Frames to complete its Job is not shown in the Timeline
Reproducible with: 2017.4.27f1, 2018.4.1f1, 2019.1.3f1, 2019.2.0b4, 2019.3.0a3
Notes:
If Scene is played with Script already enabled, it does not show the real problem
It can take more than one time to see the problem
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a7