http://bugs.winehq.org/show_bug.cgi?id=20549
Summary: secur32 memory leak on exit? Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Keywords: download Severity: normal Priority: P2 Component: secur32 AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
Valgrinding the chromium net_unittests (particularly, the ftp and http tests) yields definite leak reports like this:
664 bytes in 1 blocks are definitely lost in loss record 864 of 968 at malloc (vg_replace_malloc.c:195) by 0x101657FF: ??? ... by 0x100F0324: ??? by SECUR32_initSchannelSP (schannel.c:1376) by SECUR32_initializeProviders (secur32.c:559) by DllMain (secur32.c:1178)
This doesn't seem like a big deal, but it is a bit of a mystery, since the DLL clearly tries to free that memory on unload.
http://bugs.winehq.org/show_bug.cgi?id=20549
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Juan Lang juan_lang@yahoo.com 2009-11-02 13:14:01 --- That would be a problem in gnutls, then, not in schannel. Here's confirmation of it on their mailing lists, from 2005: http://arkiv.netbsd.se/?ml=gnutls-dev&a=2005-02&m=2789984
In brief, the following program leaks memory: int main() { gnutls_global_init(); gnutls_global_deinit(); return 0; }
There was a bunch of arguing about it, e.g. here: http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/1394
The upshot is, they don't think it's a bug, since the memory gets freed when the process exits. I think you should suppress this one.
http://bugs.winehq.org/show_bug.cgi?id=20549
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2009-11-03 00:58:05 --- Closing invalid.