Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a15
Issue ID
1200819
Regression
Yes
[Vulkan] Crash in vk::CommandBuffer::WriteTimestamp when opening Editor in Vulkan
To reproduce:
Create a new project with -force-vulkan
CRASH!
Reproduced in 2020.1.0a15
Not reproduced in 2020.1.0a14
Note: Changesets of both versions in the edit below
Reproduced in Windows 10 and Linux
#0 0x00562086ed91bd in vk::CommandBuffer::WriteTimestamp(VkPipelineStageFlagBits, VkQueryPool_T, unsigned int)
#1 0x00562086e95ec0 in GfxDeviceVKBase::GpuRecorderWriteGpuTimestampCommandInternal(unsigned int)
#2 0x00562087ff5a55 in GpuRecorderManager::FrameTick(GfxDevice&)
#3 0x00562088fddc31 in Application::TickTimer()
#4 0x00562089acb65b in MainMessageIteration(void)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment