FIX: An application that uses the WASAPI may crash when you call the GetBuffer function
Consider the following scenario:
- You write an application that uses the Windows Audio Session API (WASAPI) to manage the audio output of an application to an audio endpoint device.
- The audio endpoint is opened in exclusive mode by using the IAudioClient::Initialize method together with the AUDCLNT_SHAREMODE_EXCLUSIVE SHAREMODE flag
- You render or capture samples from this audio endpoint by using the IAudioCaptureClient interface and by calling the GetBuffer function.
In this scenario, the client application may crash when you call the GetBuffer function.
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB957569.