https://bugs.winehq.org/show_bug.cgi?id=38440
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #3 from Sebastian Lackner sebastian@fds-team.de --- I've looked at the problem in wscript and there is nothing to fix. Valgrind thinks the memory is lost because there is no pointer to the allocated memory in the process itself, but the wineserver still has a pointer (because of the queued APC). So basically a limitation of Valgrind.
I am not sure whats the best way to get rid of these warnings, blacklisting them all manually seems a bit complicated, and similar problems might also occur in ws2_32 with async io structures. On the other hand, updating something like a linked list with pending async IOs is a bit complicated, when it just has the purpose to make Valgrind happy. Anyone has a better idea?