Search Issue Tracker

Not Reproducible



Found in




Issue ID




Crash on vkGetInstanceProcAddr when consecutively executing a method for a number of meshes which creates a cropped 4K texture



Reproduction steps:
1. Download the project from the link provided in the edit
2. Open the downloaded project
3. Select all meshes in Assets/Meshes
4. Right-click on any of them and select Tools/Do some magic!

Reproducible with: 2020.1.0a8, 2020.1.0b14, 2020.2.0a16
Couldn't test versions below 2020.1.0a8, due to Unity getting stuck on importing certain textures and leaking memory

First lines of the stacktraces:

0x00007FF66AD6DDF4 (Unity) TiledTextureManager::CheckMemoryBudgetAndUpdateTiledResources
0x00007FF66AD96521 (Unity) GfxDeviceD3D12::QueuePresent
0x00007FF66AD5A759 (Unity) D3D12Window::EndRendering
0x00007FF66E14B401 (Unity) GfxDeviceWorker::RunCommand
0x00007FF66E14E0BC (Unity) GfxDeviceWorker::RunExt

0x00007FF91398768F (nvoglv64) vkGetInstanceProcAddr
0x00007FF91397B176 (nvoglv64) vkGetInstanceProcAddr
0x00007FF66235DB8B (Unity) vk::Image::CreateImageViews
0x00007FF6623A1C70 (Unity) vk::ImageManager::CreateImage
0x00007FF66235C506 (Unity) vk::Texture::Create

- The specific method takes source texture atlas in 16Kx16K and creates new cropped 4K texture with segments used only by the mesh for which the method was executed
- Memory consumption before the crash indicates possible memory leaks as it doesn't seem to consume more than 4GB of RAM when using DX11, where Vulkan and DX12 might rise up to 8-16GB of RAM usage
- Reproduces with Vulkan, DX12
- Doesn't reproduce with DX11, OpenGLCore, OpenGLES3

  1. Resolution Note (2020.3.X):

    Not reproducible on 2020.3.30f1, 2022.2.0a6

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.