Search Issue Tracker
Fixed in 2019.1
Fixed in 2018.3
Votes
0
Found in
2018.3.0a10
2019.1.0a3
Issue ID
1087222
Regression
Yes
[Profiler] Non-matching Profiler Begin/End samples for Gfx.ProcessCommands being invoked when Profiling Editor on Vulkan
To reproduce:
1. Download attached project "New Unity Project (3).zip" and open in Unity
2. Go to Edit > Settings > Player and change Graphics APIs to "Vulkan"
3. Open Profiler window
4. Press the "Profile Editor" button
5. Observe that Console becomes full of "Non matching Profiler.EndSample (BeginSample and EndSample count must match): Gfx.ProcessCommands" errors
Notes:
- This issue appears only on Windows with Vulkan Graphics API
Reproduced on Unity 2018.3.0a10, 2018.3.0b4 and 2019.1.0a3
Not reproduced on Unity 2018.1.9f2, 2018.2.11f1 and 2018.3.0a9
Regression on Unity 2018.3.0a10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
- Shader effect with specific view disappears when multiple materials in scene are present
- Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Add comment