Search Issue Tracker
Fix In Review for 2022.1.X
Votes
6
Found in
2019.4
2020.3
2021.1
2021.1.11f1
2021.2
2022.1
Issue ID
1358785
Regression
No
Gfx.WaitForPresentOnGfxThread > Semafore.WaitForSignal uses around 9 ms on almost all frames
How to reproduce it:
1. Open the user's attached project
2. Load the "Game" Scene
3. Open the Profiler window (Window > Analysis > Profiler)
4. Enter the Play Mode
5. Click on the CPU area and select stats
6. In Overview go to PlayerLoop > Gfx.WaitForPresentOnGfxThread
7. Observe the Time usage
Expected result: Semafore.WaitForSignal takes a lot less Time than 9 ms
Actual result: Semafore.WaitForSignal takes around 9 ms of Time
Reproducible with: 2019.4.29f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b10, 2022.1.0a7
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a7