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 -> unitmember this.DangerousRelease : unit -> unitPublic 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
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
