https://bugs.winehq.org/show_bug.cgi?id=36662
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- Created attachment 49347 --> https://bugs.winehq.org/attachment.cgi?id=49347 ws2_32/tests: Enter alertable state to ensure memory is released.
The attached patch should fix the last issue (the definite leak). The problem is that the thread never enters an alertable state after the APC_USER callback has been queued.
For these tests this issue wasn't really critical, since the amount of leaked memory was relatively small - but it leaves one open question: Is the same also required on Windows? I've never seen any Windows network apps that have to care about that manually. I somehow suspect that on Windows some of the internal network commands use alertable waits .... any ideas?