SafeHandle.DangerousRelease Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Manually decrements the reference counter on a SafeHandle instance.
public:
void DangerousRelease();
[System.Security.SecurityCritical]
public void DangerousRelease ();
public void DangerousRelease ();
[<System.Security.SecurityCritical>]
member this.DangerousRelease : unit -> unit
member this.DangerousRelease : unit -> unit
Public Sub DangerousRelease ()
- Attributes
Remarks
The DangerousRelease method is the counterpart to DangerousAddRef. You should always match a call to the DangerousRelease method with a successful call to DangerousAddRef.
Caution
In the same way that unmatched DangerousAddRef calls can cause resource leaks, unmatched DangerousRelease calls can cause invalid handle states to become visible to other threads.
Applies to
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for