You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using wgpu on macos/metal, and when I call write_buffer on a different thread from get_current_texture, about 20% of the calls to write_buffer will block both calls for an extra ~16 ms. Here's a screenshot of puffin viewer showing the problem:
It looks like write_buffer might be taking a lock at just the wrong moment and causing get_current_texture to miss the screen refresh, and locking up both threads until the next screen refresh.
The text was updated successfully, but these errors were encountered:
danielkeller
changed the title
write_buffer on antother thread can block get_current_texture for an extra frame
write_buffer on another thread can block get_current_texture for an extra frame
Jan 15, 2022
I'm using wgpu on macos/metal, and when I call write_buffer on a different thread from get_current_texture, about 20% of the calls to write_buffer will block both calls for an extra ~16 ms. Here's a screenshot of puffin viewer showing the problem:
It looks like write_buffer might be taking a lock at just the wrong moment and causing get_current_texture to miss the screen refresh, and locking up both threads until the next screen refresh.
The text was updated successfully, but these errors were encountered: