05-13-2008 06:56 AM
Don't know if this will work for you or not but have you tried debugging your plugin in vs.net ?
vs.net 2008 TFS Edition has profiling tools that you can then use to identify hotspots in your code which could lead to identifying memory leaks.
06-02-2008 08:04 AM
In VS build the app with full debug info. The under the projects properties under debug start the external program actsage.exe in the program directory. You can then step through your code as it runs in the debugger. There's a good post on how to do this in the blogs section of actdevnet somewhere. I think its called someting like debuggin a custom plugin.