There is NO safe way to kill a task on the Amiga, whether it is OS3.1 or OS4. If you kill a task using Scout, it will eventually kill your system. And you don't get its resources back.
Linux and Unix can do it because they use an entirely different kernel design - the Amiga uses a shared address space and so you can never know what resources were allocated by a task. We can't ever copy the Linux way if we want to stay even remotely backward compatible, so there is no way to kill tasks...
...unless you go the Windows way. Namely, you allocate lots of memory and VM to track all the resources a task allocates so you can free them later. As far as I'm concerned, the loss of efficiency this would cause to AmigaOS wouldn't be worth it. Windows is horribly slow and is only propped up by its hardware. Copying it would only make AmigaOS unusable.
On an Amiga, there is only one way to stop things crashing - coders must learn how to code properly. There's no excuse for sloppy coding.
