BUG: Shell enters unresponsive state (can't close it)

[Raziel]

CLI 52.4 (10.05.2007)

Not sure if this is intended behaviour, but at least there is one bug to this.

I can make the Amigashell enter an unresponsive state, at least when it comes to closing it, in a pretty easy way.

Steps to reproduce:
1) Open Amigashell by either running CLI or using the Shell(.info) "frontend"
2) Type "ping duckduckgo.com" into the shell window
3) Instead of pressing ENTER, close the shell window

Expected Behaviour: The shell closes as i told it to

Actual Behaviour: The shell executes the command i typed in, rendering the whole shell window unresponsive to
a) a CTRL-C to stop the command from working, actually i cannot type anything in this window anymore
b) closing the shell window et al which leaves me with a running command i can't stop and an open shell window i cannot close.

--> I can open another shell tab, but i still can't close the shell window.

[nbache]

You can always stop the command by entering "break (processno) c" in another shell window or tab. If you don't know the process number, it can be found with "status".

As for the behaviour when closing, I believe it is "how it works". Closing the shell is just another command you send after the one you entered.

But I'd prefer if one of the experts could explain it better (Tony? Colin?).

BTW, I doubt the CLI is the module containing this behaviour.


Best regards,

Niels

[Raziel]

@nbache
Breaking the process from another shell is working, thanks for the workaround, still it's rather awkward to not be able to do it from the running process window and therefore i still consider this as bug as input there is obviously rejected for some reason.

CLI was just the program that came to mind, if you need me to check another programs versions i'll stand by

[tonyw]

Raziel:

I had this problem in the con-handler years ago, and I thought I'd fixed it. I shall have to go back through my old BZs.

As Niels said, it can happen if you start something new after closing the session. It can't finish closing while the "new" thing is running and since it has started closing, it can't hear or respond to any input. Maybe there is still a path from "normal ops" to unresponsive.

BTW, what are the versions of your con-handler and console? Just do Project/About in the Shell.

[nbache]

Raziel:

I had this problem in the con-handler years ago, and I thought I'd fixed it. I shall have to go back through my old BZs.

Well, at least I could reproduce the issue as described above, using the latest betas.

Best regards,

Niels

[Raziel]

Raziel:

I had this problem in the con-handler years ago, and I thought I'd fixed it. I shall have to go back through my old BZs.

As Niels said, it can happen if you start something new after closing the session. It can't finish closing while the "new" thing is running and since it has started closing, it can't hear or respond to any input. Maybe there is still a path from "normal ops" to unresponsive.

BTW, what are the versions of your con-handler and console? Just do Project/About in the Shell.

Ah, that exactly explains my problem, thank you for confirming it

Con-handler 53.78 (14.04.2016)
Console.device 53.99 (5.05.2016)

@nbache

Thank you aswell for confirming it