I think the issue was by ths following , Turning confirmation prompts off globally disabled many other useful checks, such as the one to ask you if you really want to delete all breakpoints when you type "delete". It would be better to disable the prompt only for the quit command. You can do that by adding this hook to your ~/.gdbinit (for current user) or /etc/gdb/gdbinit (for all users):
set confirm off
If I kill a System.Diagnostics.Process with .Kill(), do I also need to call .Close()?
I think the issue was by ths following , System.Diagnostics.Process implements IDisposable via the Component class, and the protected Dispose(bool) method calls Close(). It is generally considered good practice to dispose of disposable resources when you are done with them, as this will immediately release any resources associated with the class (not having to wait for the GC to run). So to answer your question:
I think the issue was by ths following , You don't. It's not up to you when the plugin process should end, it's up to the browser. Chrome, for instance, keeps plugin processes alive for a short time to avoid thrashing if someone, say, reloads a page with the only instance of the plugin, or navigates between two pages with the same plugin. Your bug isn't that the process is staying alive for a while, it's that it's crashing when it does exit. You should debug and fix your crash.
Android Studio - How to ( close, quit, exit, kill, etc.) an application