Closed skoruppa closed 5 years ago
This floating point exception before getting to the game's main menu bisects to:
commit a7d48718466978bd5a6ae73d9cf1c2ea566d772c
Author: Jason Ekstrand <jason.ekstrand@intel.com>
Date: Wed Feb 20 18:14:56 2019 -0600
anv/pipeline: Sort bindings by most used first
This commit just sorts the bindings by how often they're used vs the
array size of the binding. This will let us make more nuanced decisions
about what goes in the binding table vs. what to make bindless.
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
:040000 040000 6cbf6a670b34fa473b820ed7672eff3c1bf66982 2feb952dfdbd87127888534a49f84fafb3b037c2 M src
@jekstrand, can you check if you can reproduce this?
Looking at this a little bit more on my test boxes, I think that there's been a recent game change that's exposed a behavior difference between mesa 19.0 and 19.1 rather than a driver regression that fell through the cracks.
-vulkan_disable_steam_shader_cache should workaround it for now. We are aware of this bug and are investigating. @Plagman
It could also be an issue in our pipeline cache where it's not caching something properly. That's kind-of an odd commit for such an issue to bisect to, thought.
It could also be an issue in our pipeline cache where it's not caching something properly. That's kind-of an odd commit for such an issue to bisect to, thought.
We have identified that we have a pipeline being created with a descriptor set layout that is missing a binding. It fails validation and crashes ANV and AMDVLK, but not RADV or NVIDIA. It's still our bug though. The problem we're working on is identifying how the bad descriptor set layout got in the cache and what we can do to filter it out.
@HansKristian-Work said that "Intel ANV crashes on a pipeline which fails validation. I built driver with debug and the crash makes sense. The shader is accessing a texture which does not exist in the pipeline layout. I inspected the shader + layout information and it's faulty indeed."
This is fixed, closing.
Your system information
Steam
->Help
->System Information
) in a gist: https://gist.github.com/skoruppa/6797ff4688d4f27c4c74c800fad35fb8Please describe your issue in as much detail as possible:
Using mesa 19.1.0 when Vulkan is enabled, the game just crashes right after launching
crash_20190626215542_1.zip
Steps for reproducing this issue: