Search Issue Tracker
Won't Fix
Votes
3
Found in [Package]
5.3.1
Issue ID
1168417
Regression
Yes
[Metal][HDRP]Editor activity spikes on Semaphore.WaitForSignal when Shader Graph window is open and undocked
How to reproduce:
1. Open the attached project ("HDRP_Performance")
2. Open the Profiler and enable the Profile Editor
3. In Profiler, select the Hierarchy preview
4. In Profiler search field type Semaphore.WaitForSignal and press record
5. In Assets, double click on the "TestShaderGraph" and make sure that Shader Graph window is undocked
6. Observe the Profiler
Expected result: Semaphore.WaitForSignal does not spike
Actual result: Random Semaphore.WaitForSignal spikes are visible
Reproducible with: 2019.1.9f1(HDRP 5.7.2, Shader Graph 5.7.2), 2019.2.0b7(HDRP 6.7.1, Shader Graph 6.5.2), 2019.3.0a9(HDRP 6.5.2, Shader Graph 6.5.2)
Not reproducible with: 2018.4.4f1(HDRP 4.1.0, Shader Graph 4.10.0), 2019.1.0b6(HDRP 5.2.3, Shader Graph 5.2.3)
Notes:
- On 2019.3.0a9, the issue is reproducible without any undocked windows
- Testing 2019.2.0a6 and earlier resulted in inconsistent reproduction, most likely due to the inconsistencies of HDRP compatibility
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:
Please try to use the new Profiler Out Of Process (see profiler user preferences) and see if it helps and reduces the noise and lag of the profiler window itself while profiling.