windows - winverifytrust memory leak -
windows - winverifytrust memory leak -
i had question on winverifytrust's catalog signing. using winverifytrust , don't phone call wtd_action_state_close after call, phone call if hwvtstatedata not null. see scheme memory consumption continues rising in spikes
the consumption rises, settles downwards steady state , rises 1 time again after time , rises 1 time again after longer period larger amount. believe may side-effect of internal caching done catalog signature trust api. help confirm behaviour
is expected behaviour?
is our usage of api (not calling state_action_close unconditionally correct?)
does internal caching behave way, if reach steady state cache size not grow beyond limit, can limit predicted?
fyi: looked @ topic memory leak while verifying authenticode signature of executables? well, give-and-take there not conclusive , not related catalog signing, hence new question
http://msdn.microsoft.com/en-us/library/windows/desktop/aa388205%28v=vs.85%29.aspx
free hwvtstatedata fellow member allocated wtd_stateaction_verify action. this action must specified every utilize of wtd_stateaction_verify action.
windows memory-leaks winverifytrust
Comments
Post a Comment