Skip to content

v3dv: use NULL for vk_error on initialization failures

This commit fixes two issues:

  • On CreateInstance, we are freeing the instance, and then trying to use it when calling vk_error. This could be problematic, so let's just use NULL.

  • On CreateDevice, we are getting a unsupported feature error, and then trying to call vk_error using the instance. That's is not really a instance error, and will assert when the ongoing common vk_error lands mesa. Let's use NULL instead, as the object it applies, the device, was not created.

Merge request reports