-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Can't kill "not responding" apps #38
Comments
Wouldn't the inclusion of this feature be redundant? It's already supported on Windows anyway. Edit: Looks like it only is supported on the newest version though... |
It's not possible because windows freezes that program and no application can access it, while it's not responding. |
If I have SuperF4 elevated, trying to kill not responding apps will kill my display driver. |
The windows error reporter instantly pops up when I press Ctrl. I can't close the error reporter, nor can I normally close the fullscreen app with alt+F4. Maybe if there was an option to change the combination key? |
Yup, can report the same issue on my side. |
When I want to kill a application, most of the time it's not responding. It would be good if we had ability to kill the not responding apps. |
Alright, I found the solution, we can use AutoHotkey to kill the unresponsive apps. The hotkey is
|
Hi, I've been using this software and I find it useful. One problem, I cannot kill the app that is not responding (I've tried xkill / TimerCheck / with admin), only way to properly force close is launch Task Manager and kill this process. I'm guessing the SuperF4 thinks that unresponsive window is "inactive" which cannot be killed? I'm using SuperF4 1.4 on Windows 10.
I have an idea for improvement - use the Alt+Tab method to easily kill the app process while the window (including the unresponsive one) is highlighted then hit F4, here's an example of using Alt+Tab and Del to close the highlighted window.
The text was updated successfully, but these errors were encountered: