Skip to content

Sequence: reset mIsRunning on exception from submit/waitForFences#461

Open
mgajda wants to merge 1 commit intoKomputeProject:masterfrom
mgajda:fix-device-lost-simple
Open

Sequence: reset mIsRunning on exception from submit/waitForFences#461
mgajda wants to merge 1 commit intoKomputeProject:masterfrom
mgajda:fix-device-lost-simple

Conversation

@mgajda
Copy link
Copy Markdown

@mgajda mgajda commented Apr 21, 2026

Fixes #459.

mIsRunning is set true before vkQueueSubmit / vkWaitForFences but not reset on throw, deadlocking the next call. Catch-and-rethrow clears it; the exception propagates unchanged.

Supersedes #460.

When vkQueueSubmit or vkWaitForFences throws (e.g. vk::DeviceLostError
on GPU TDR), leaving mIsRunning=true deadlocks the next evalAsync()
call in the 'already running' guard. Catch-and-rethrow so the state
is cleared and the exception still propagates to the caller.

Fixes KomputeProject#459.
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.

Add VK_ERROR_DEVICE_LOST exception handling

1 participant