-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLOSE option does not work anymore #17
Comments
It is likely waiting on the leak window, which can take a long time to generate. |
The leak window is created when you add the line to your app, Deputy watches for the window. Is there a second form on the application? Possibly the code is not sending close to the main form, I will have to review and see if I can re-produce. |
Yes, the application has multiple forms. On the other hand, with a single-form application, Deputy CLOSES the application without waiting for any "leak window." BTW, I have never seen any "leak window." The feature to wait for a "leak window" is turned OFF anyway. So Deputy shouldn't wait for any "leak window." No " leak window " is shown even when I willingly create a memory leak by not freeing a created object, no "leak window" is shown. So I am not sure what you mean by "leak window." |
I suspect that something changed with the way handles are returned when I try to find the main form window. I will work to produce a minimal sample, I use this function as well but do not experience the problem. Possibly changing the application main form to the second form will help me to re-produce the issue. Expect a status update around April 15, a previous release has my resources at this point. |
Hello SwiftExpat,
In the beginning, the Process Manager's CLOSE option did work perfectly.
But the CLOSE option no longer works for some time now, and I always have to FORCE TERMINATE my program.
How can I find out why the CLOSE option does not work?
Of course, the CLOSE option is enabled:
![image](https://user-images.githubusercontent.com/5140376/227194413-e66d9f8a-f3c4-45a9-ac9d-285fc2f8697b.png)
The text was updated successfully, but these errors were encountered: