Home/ Questions/Q 545719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T10:47:29+00:00

I have unmanaged code that calls an asynchronous managed method that returns a handle,

  • 0

I have unmanaged code that calls an asynchronous managed method that returns a handle, and then the unmanaged code uses that handle to wait.
According to the documentation, SafeWaitHandle provides 2 other methods (DangerousAddRef and DangerousRelease ).
Should I use these methods in order to prevent the Handle from not being released? As the name of the method DangerousGetHandle suggest, it seems to me that I should be very careful with something, what is so dangerous here?

Edit: Is there a better way to implement this scenario (not dangerously)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If the managed method returns the handle, but doesn’t pass ownership of the handle to the calling unmanaged method, then you should just return the handle as a SafeWaitHandle directly (it will be marshalled to a handle) – this way unmanaged code doesn’t have to worry about releasing the handle.
    If you want to pass ownership of the handle to the unmanaged method, then you should call DangerousAddRef before returning the handle, but then you have to release the handle using unmanaged code.

    • 0