Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wrong timeout value at vkAcquireNextImageKHR() #51

Open
parkhw00 opened this issue Aug 3, 2021 · 1 comment
Open

wrong timeout value at vkAcquireNextImageKHR() #51

parkhw00 opened this issue Aug 3, 2021 · 1 comment

Comments

@parkhw00
Copy link

parkhw00 commented Aug 3, 2021

vkAcquireNextImageKHR() function accepts timeout value in nano-second unit. But, the timeout value is used as milli-second unit at mainloop_wayland(), mainloop_xcb() function as follow.

  result = vkAcquireNextImageKHR(vc->device, vc->swap_chain, 60,
                                 vc->semaphore, VK_NULL_HANDLE, &index);
  if (result != VK_SUCCESS)
     return;

Such a too short timeout value(60ns) causes program termination when screen lock or some other unstable compositor running.

@zmike
Copy link

zmike commented Sep 12, 2023

Yeah this timeout is not viable for real hardware.

@kusma kusma mentioned this issue Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants