Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.3.0b5
Issue ID
960893
Regression
Yes
[Vulkan] Crash on UnityMain when launching Standalone Player that uses Vulkan API
How to reproduce:
1. Open any project
2. Set Graphics API to Vulkan
3. Build and Run Standalone
4. Launch Player
Stack trace from output_log.txt:
0x00007FF9BE1368FA (UnityPlayer) GfxDisplayVK::Setup
0x00007FF9BE0FBBF8 (UnityPlayer) GfxDeviceWorker::RunCommand
0x00007FF9BE10407B (UnityPlayer) GfxDeviceWorker::RunExt
0x00007FF9BE10413C (UnityPlayer) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF9BDB9BD48 (UnityPlayer) Thread::RunThreadWrapper
0x00007FFA00BC2774 (KERNEL32) BaseThreadInitThunk
0x00007FFA016E0D51 (ntdll) RtlUserThreadStart
Reproduced with: 2017.1.2p2, 2017.3.0b5, 2017.3.0b6, 2018.1.0a1
Not reproducible with 2017.1.2p1, 2017.2.0f3, 2017.3.0b4
Regression introduced in: 2017.3.0b5
Fixed in: 2017.3.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
Add comment