I have successfully compiled LunarG’s VulkanSDK’s cube example. When running the cube application, I noticed the following issues:
- When I try to move cube's window, there appears a lot of lag (refreshing was delayed).
- While resizing the cube's window, the cube's window turns black and only shows the rotating cube when the resizing stops.
- When I click on a background GUI, the screen freezes for a moment. Example, rotating cube will stop rotating, and all GUI becomes unresponsive. Then the clicked GUI moves forward and cube resume rotation. When I move this GUI around the screen with mouse, the cube's rotation is affected. It stutters.
LunarG rep thinks these issues are caused by display manager or IHV drivers. He observed the same issues with unity desktop manager but much less in gnome desktop. In my case, I noticed this error in dmesg after running vulkan application:
[ 7427.461365] [drm:nvidia_drm_gem_prime_fence_init [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fencing init: 0x00000004
[ 8536.059214] [drm:nvidia_drm_gem_prime_fence_init [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fencing init: 0x00000004
[ 8798.572087] [drm:nvidia_drm_gem_prime_fence_init [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fencing init: 0x00000004
I executed vulkansdk’s cube application three times, got the same error thrice.
Using VulkanSDK version 1.0.46.0, Ubuntu 16.04.2, Kernel 4.8.0-46-generic, and Nvidia drivers 375.39 and 381.09.
Questions:
- What does the Nvidia error means and how can it be fixed?
- Is the error causing the 3 issues I had mentioned earlier?
- If not, is nvidia’s driver causing them?