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

examples/triangle.rs running as fast as 3378 fps, locks up PC #1210

Closed
SongWithoutWords opened this issue Jun 27, 2019 · 3 comments
Closed

Comments

@SongWithoutWords
Copy link

SongWithoutWords commented Jun 27, 2019

  • Version of vulkano: 0.12.0
  • OS: Linux, Ubuntu 18.10
  • GPU (the selected PhysicalDevice): GTX 1050
  • GPU Driver: Nvidia 390.116
  • Upload of a reasonably minimal complete main.rs file that demonstrates the issue: vulkano/examples/src/bin/triangle.rs
  • Device: Laptop (Dell XPS 15 9570)

I launched the triangle.rs example and it locked up my machine.

I then googled around for this issue, and followed the advice in #923 by calling wait on the future after signal_fence_and_flush(), but the issue remained.

I then added some timing code to it and found that it was running as fast as 3378 fps.

Can this library be made to work with Nvidia drivers on Linux?

@SongWithoutWords
Copy link
Author

I just tried to repro this on another machine, a desktop rather than a laptop using a GTX 1070 instead of a GTX 1050, but with the same versions of the same drivers and operating system.

Without the call to wait() after signal_fence_and_flush(), it monopolized one core of the CPU (utilizing 25%) without locking up the whole machine. After calling wait() after signal_fence_and_flush(), it now uses 1-2% of the CPU time.

So this issue seems hardware dependent.

@faulesocke
Copy link

This sounds definitely like a bug in the Nvidia driver. At least with the wait call you should never get a lockup and of course you shouldn't without the wait. Maybe point Nvidia towards this issue?

@AustinJ235
Copy link
Member

This is a known issue, please refer to #1247

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

3 participants