Further testing suggests it is ScaleMT which is leaking: PictureMBS.ScaleMT() leaks handles, but the # of handles seems variable - perhaps there's some race-condition or timing dependency in the code? I see it leak 2, 3, or 5 handles on repeated runs.
PictureMBS.Scale() doesn't leak at all. On Dec 14, 2014, at 1:18 PM, Michael Diehr <m...@xochi.com> wrote: > Hi Christian, > > I'm trying to track down a leak of Handle objects in Win32, and the first > thing I'm seeing is that after running: > > PictureMBS.ScaleMT(0,...) > > I end up with 3 or 4 more handles than I started with. > > I'm using Windows Task Manager / Processes tab with "View/Select Columns..." > set to show Handle count. Tested on a Win7x64 VM with 2 CPUs. > > This is with MBS 14.4 release. > > Can you check to see if there are any obvious places in your code where you > forget to release a handle? > > > _______________________________________________ > Mbsplugins_monkeybreadsoftware.info mailing list > mbsplugins@monkeybreadsoftware.info > https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list mbsplugins@monkeybreadsoftware.info https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
