Skip to content
New issue

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

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

Already on GitHub? # to your account

Panic in CpuBufferPoolChunk::clone #1733

Closed
Tenebryo opened this issue Oct 22, 2021 · 0 comments · Fixed by #2127
Closed

Panic in CpuBufferPoolChunk::clone #1733

Tenebryo opened this issue Oct 22, 2021 · 0 comments · Fixed by #2127

Comments

@Tenebryo
Copy link
Contributor

  • Version of vulkano: 0.24.0
  • OS: Win 10 x64
  • GPU (the selected PhysicalDevice): RTX 2070 Super
  • GPU Driver: 496.13

Issue

I'm getting a panic when cloning a CpuBufferPoolChunk, where the corresponding ActualBufferChunk cannot be found. The only way I could find that this would be possible was for the entry in the ActualBuffer to be removed when there are still multiple references to it.

The panic in question happens at https://github.com/vulkano-rs/vulkano/blob/v0.24.0/vulkano/src/buffer/cpu_pool.rs#L602

Additionally, the issue doesn't trigger when I run the debug build, but does when I run the release build. This suggests to me that there is some race condition, since the debug build runs slower than the release build, but I don't really understand what could cause this.

Is there a workaround or would the newer versions of vulkano fix this?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant