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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment