Find out why ASF has CPU infinite loop on terminal detach

[JustArchi]

Checklist

• [X] I read and understood ASF's Contributing guidelines
• [X] I also read Setting-up and FAQ, I don't need help, this is a bug report
• [X] I don't own more than 10 accounts in total
• [X] I'm not using custom plugins
• [X] This is not a question
• [X] This is not a technical issue
• [X] This is not ASF-ui problem

ASF version

Latest stable release

ASF variant

linux-x64

Bug description

Issue https://github.com/JustArchiNET/ArchiSteamFarm/issues/3050 highlighted a problem where background ASF process on Linux after restart and detaching console runs into 100% CPU utilization. I've reproduced it myself so the issue seems global enough.

Expected behavior

ASF should run in the background normally.

Actual behavior

There is a thread taking 100% CPU allocation, we should find out if it's anything related to us we can fix, or whether this is .NET issue.

Steps to reproduce

• Start ASF in Linux terminal as usual
• Type c to enter command mode and use restart command
• Observe old ASF shutting down and new ASF being launched, which is no longer attached to the console (but still printing to it)
• Close terminal
• ASF process in the background is now using 100% CPU, best part is it seems to work correctly

Possible reason/solution

No response

Can you help us with this bug report?

Yes, I can code the solution myself and send a pull request

Full log.txt recorded during reproducing the problem

Not relevant

Global ASF.json config file

No response

BotName.json config of all affected bot instances

No response

Additional info

No response

[JustArchi]

After investigation: Linux terminal for some unknown to me reason sends 0 all the time as console input, this causes our interactive console listener to go into loop, because it now has work of reading 0 input infinitely. ASF logic works correctly, but why the hell something like that happens is unknown to me as of now, will need to code some workaround for that.

[JustArchi]

@andreldmonteiro I've found the root culprit and managed to code a workaround for that, big thanks for report! This should no longer happen starting from ASF V5.4.12.6.