Skip to content

Conversation

@cwfitzgerald
Copy link
Member

Connections

Closes #8310
Backport to v27 #8419
Backport to v26 #8414

Description

This prevents frame pacing issues on vulkan/windows. See upstream issue for more information.

Testing

Manually tested

Squash or Rebase?

Izzacommit.

Checklist

Changelogs will be handled in backports.

@ErichDonGubler ErichDonGubler merged commit b3d9431 into gfx-rs:trunk Oct 23, 2025
41 checks passed
@ErichDonGubler
Copy link
Member

I'm not sure that I understand the note about the changelog, except in really specific case. Why does a backport mean we shouldn't include it in the mainline changelog? Are you only planning on omitting changelog entries when we're backporting to the most recent release branch?

@cwfitzgerald
Copy link
Member Author

I will have changelog entries for the v26 backport, and the v27 backport, but for v28 from a user's perspective it will have been "already fixed in v27".

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

Successfully merging this pull request may close these issues.

FIFO present modes lead to a long wait for semaphores on Vulkan

2 participants