Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2019.4.26f1
2020.3
2021.1
Issue ID
1337930
Regression
Yes
Crash on vk::DataBuffer::CreateResource when opening project on machine with a weaker GPU
Reproduction steps:
1. Download the project from the attached link
2. Open "RunRepro.py" located in the project folder
3. Edit line 17 to be "projectPath = scriptDir"
4. Edit "RunRepro.bat" to point to "Python.exe" on your machine
5. Open the Command Prompt
6. Run the following command "<Path_To_Project_Folder>\RunRepro.bat -e "<Path_To_Unity_Exe>""
Reproducible with: 2019.4.28f1, 2020.3.11f1, 2021.1.10f1
Not reproducible with: 2018.4.35f1, 2021.2.0a19
First lines of the stack trace:
0x00007FF770E85BC0 (Unity) vk::DataBuffer::CreateResource
0x00007FF770E876A5 (Unity) vk::DataBuffer::Initialize
0x00007FF770E4DCEA (Unity) GfxDeviceVK::InitializeBufferInternal
0x00007FF770DE90B7 (Unity) GfxDeviceWorker::RunCommand
0x00007FF770DED2FC (Unity) GfxDeviceWorker::RunExt
Notes:
- On successfully reproducing the issue, red text that reads "Bug Reproduced" will be shown in the Console
- The provided "RunRepro.bat" is set up to point to "C:\Python39\Python.exe" as the installation of Python 3.9
- The issue was reproduced on a machine with an NVIDIA GeForce GTX 960 4GB GPU
- From what we currently know, a GPU with 4GB or less VRAM is required to reproduce the crash
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a1