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

Explicitly track active renderer instead of relying on vid_rtx. #199

Merged
merged 1 commit into from
Mar 3, 2022

Conversation

res2k
Copy link
Contributor

@res2k res2k commented Mar 3, 2022

A lot of code assumes the value of vid_rtx also reflects the current renderer.
However, it can happen that this is not the case, causing code to rely on this
assumption to break (see #198).

Address by explicitly storing the currently active renderer and updating that
field on renderer initialization/shutdown. Also change any code that used vid_rtx
to check the renderer to use that new value.

A lot of code assumes the value of vid_rtx also reflects the current renderer.
However, it can happen that this is not the case, causing code to rely on this
assumption to break (see NVIDIA#198).

Address by explicitly storing the currently active renderer and updating that
field on renderer initialization/shutdown. Also change any code that used vid_rtx
to check the renderer to use that new value.
@apanteleev apanteleev merged commit 5849739 into NVIDIA:master Mar 3, 2022
@res2k res2k deleted the active-ref-tracking branch March 3, 2022 21:25
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.

2 participants