Timeline for How to kill all obtrusive messagebox recursion manually when they are opened very quickly and very many in Windows
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2015 at 9:47 | comment | added | DMaster | I didn't knew this before, thank you! | |
| May 14, 2015 at 1:28 | comment | added | Karan |
What you've described is basically a fork bomb, and even on Linux it can exhaust resources quickly if ulimit -u is not used. For the record I had Firefox running and Word and Notepad open with unsaved files, and was able to log off. Windows then showed me that it was killing all the instances of your program, and when all were gone I quickly cancelled the log off and was able to continue my work without any problems.
|
|
| May 13, 2015 at 6:20 | comment | added | DMaster | It seems Windows does not provides enough tools for secure control, sometimes user must surrender. Where is a helpful tool which help me to undo this accident? | |
| May 12, 2015 at 17:56 | comment | added | Karan | Yes, but when you have an aggressive process hogging all resources by opening multiple instances, pretty soon you'll be able to do nothing as the system will become near-unresponsive. If possible you can quickly close apps and answer Yes when they ask to save, then log off. That, or try and open Task Manager and somehow kill the process, but that might be difficult if it keeps spawning new windows that overlap or steal the focus. | |
| May 12, 2015 at 9:18 | history | edited | DMaster | CC BY-SA 3.0 |
edited body
|
| May 12, 2015 at 8:37 | comment | added | DMaster | But logging off may cause unsaved data lost | |
| May 11, 2015 at 20:08 | comment | added | Karan | Task Manager doesn't work to kill the program? If that's the case you might need to log off. | |
| May 10, 2015 at 14:06 | review | First posts | |||
| May 10, 2015 at 19:23 | |||||
| May 10, 2015 at 13:58 | history | asked | DMaster | CC BY-SA 3.0 |