Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,219 questions
PlaySound has a Memory Leak when called
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 19%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Shirley
21
Reputation points
I have a demo project where I first call
PlaySound (L "High_A. wav", NULL, SND_ASYNC | SND_LOOP);
to play the audio in a loop, and then call
PlaySound (NULL, NULL, NULL) to stop playing.
When I call PlaySound(L "High_A.wav", NULL, SND_ASYNC | SND_LOOP) again. And I found that the Memory (active private working set) and Page faults of audiodg. exe had both increased in the task manager.
After repeating the above operation multiple times, the Memory (active private working set) of audiodg. exe slowly increased and could not be released. Page faults always increase and no release.
Why? Am I using it incorrectly?
Windows API - Win32
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,171 questions
{count} votes
-
Jeanine Zhang-MSFT 6,956 Reputation points Microsoft Vendor2023-09-13T07:41:33.63+00:00 PlaySound does not have a memory leak. As far as I'm concerned, you couldn't get through audiodg.exe to determine that PlaySound has a memory leak.
The memory occupied by audiodg.exe will not be released. You could refer to the threads:
-
Jeanine Zhang-MSFT 6,956 Reputation points Microsoft Vendor
2023-09-15T08:34:10.49+00:00 Have you got any updates about this issue? Could you please check my suggestion?
Sign in to comment