Deputy 2.5 series release(s) support include:
- Sending a close message to allow for a clean shutdown. This feature was requested on GitHub, issue 1.
- Cleaner use of message window. Requested via email feedback.
- Updates are cached via new update manager class.
- Source code is restructured to be easier to follow as an example of a TOTAL plugin
Deputy is now available as individual component of RunTime ToolKit. Purchase Info
Thanks to all who gave feedback on the 2.4 series, as always feedback is appreciated on GitHub,
Close Message - clean shutdown
Deputy now has 2 options for process remediation, terminate and close. A feature was requested on GitHub as issue 1 and after evaluation it made for a cleaner second option for process remediation. Deputy now has a configuration form that allows you to choose classic terminate or close. The close option sends a close message to the window and then waits for the process to exit or display memory leak detail and optionally captures the message leak detail. The memory leak is captured using clipboard messages and a short wait.
Configuration Options
Close Activity Monitor
While waiting for the application to close a window is displayed. To prevent flicker in the IDE, this windows is only shown after 200ms, open issue #3, feedback appreciated.
Open Issue, Issue 4, allow to force terminate. Currently the expert sends the close, and then loops till the process exits. This should have a overall timeout and an option to force close.
Leak History
Review of your memory leak report is provided by the status (last remediation / memory leak) or history (all captured leaks) tabs.
Observations
Force terminate is the next priority, currently when the app does not respond to close you have to go to Task Manager.
The clipboard usage is works based on a sleep, so it is not a 100% solution. Possibly on a loaded machine the copy in the client app does not get to the clipboard before I call paste in the IDE.
Feedback is appreciated on GitHub,