http://bugs.winehq.org/show_bug.cgi?id=20684 Dan Kegel <dank(a)kegel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #3 from Dan Kegel <dank(a)kegel.com> 2009-11-13 12:51:32 --- Adding that to the little test case gets rid of the leak there, but the real code already has the proper number of calls to CryptReleaseContext, and leaks anyway, so maybe something more subtle is going on. To repeat: $ wget http://kegel.com/wine/chromium/chromium-tests.tar.bz2 $ tar -xjvf chromium-tests.tar.bz2 $ valgrind --leak-check=full --trace-children=yes wine src/chrome/Debug/base_unittests --gtest_filter=SignatureCreatorTest.* I added log statements to show where the keys and context were acquired and released, and will attach log files. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.