Memory Leak surviving terminated process
Joined: 07 October 2016
Posted: 07 October 2016 at 8:33pm
Have one very old App I am lazy to rewrite because it works perfectly except it creates memory leak in system somewhere after application it self has been terminated.
Manifestation: after extreme use of this application (over 300 starts) application is unable to subclass ListBox object and perfrom custom drawing any more, and it reverts back to internal draw procedure but it keeps subclassed styles (wierd becouse AppHook still works, setting styles+stylesex works but it's not custom drawing anymore). To resolve this issue I must reboot system.
Last several months I tried more than several times to find any kind of memory leak, in AppHooks, SubClassing, GDI objects, Handles, ... so far everything resulted in been properly released or freed.
please notice common usage of this application is right click on folder in windows explorer and run application with selected path. Perform some operation on bulk of files in that folder and/or subfolder files. And finally close application. Application doesn't even run for long maybe 1-5 minutes at max per single start. Issue is I am starting this application 50~70 times a day, so every several days I must reboot system. If I don't use this application everything is just fine.
My main question is what kind of resource usage by application can survive terminated process?
Or is there somewhere bug in system that can yield this behavior?
|Forum Jump||Forum Permissions
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum