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
The existing validation layer detects handle leaks and incorrect use of get/retain/release APIs for handle lifetime management. It's only capable of detecting use-after-free if it happens to be in one of the lifetime management calls.
Given the existing implementation that already tracks handles, the validation layer should be extended to also detect use-after-free and, in general, use of invalid handles across the entire API.
The text was updated successfully, but these errors were encountered:
pbalcer
changed the title
add support for detecting use-after-free in the validation layer (for all APIs)
Add support for detecting use-after-free in the validation layer (for all APIs)
Sep 18, 2023
The existing validation layer detects handle leaks and incorrect use of get/retain/release APIs for handle lifetime management. It's only capable of detecting use-after-free if it happens to be in one of the lifetime management calls.
Given the existing implementation that already tracks handles, the validation layer should be extended to also detect use-after-free and, in general, use of invalid handles across the entire API.
The text was updated successfully, but these errors were encountered: