From: Matthew M. <do...@us...> - 2005-01-11 07:19:25
|
python-mhash leaks memory every time on every MHASH object deletion, since it calls mhash_end without freeing the return. Attached a patch to free it. Of course, what would really be good would be a way to free a mhash "thread" without doing any of the final calculations or digest generation. I guess you can call mhash_deinit with a NULL for the second parameter, but: 1) tiger160_digest doesn't check for null param 2) Even when it does work, you still waste time doing the hash's final stuff when you don't care and all you really want is to free the thread. So, I propose a new function be added, or that mhash_deinit be patched to simply skip calling td->final_func and td->deinit_func if a NULL result is passed. -- Matthew Mueller do...@us... |