Skip to content

vulkan: Don't use set_foreach_remove when destroying pipeline caches

Friedrich Vock requested to merge pixelcluster/mesa:vulkan-pcache-no-unsafe-set-next into main

set_foreach_remove assumes no entries have been removed. That assumption only holds if no errors occur, since pipeline cache objects can get removed if an error occurs during deserialization.

This fixes dEQP-VK.api.device_init.create_instance_device_intentional_alloc_fail.basic crashing on RADV.

Merge request reports