Bug #90443 | mysqlsh using 100% cpu after tty is gone | ||
---|---|---|---|
Submitted: | 16 Apr 2018 6:24 | Modified: | 17 Apr 2018 15:12 |
Reporter: | Kenny Gryp | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Shell AdminAPI InnoDB Cluster / ReplicaSet | Severity: | S3 (Non-critical) |
Version: | 8.0.4 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[16 Apr 2018 6:24]
Kenny Gryp
[16 Apr 2018 16:33]
Alfredo Kojima
Are you able to reproduce this? Was the shell session doing something at the time? Here's what I'm trying: ssh to remote Linux host start mysqlsh one of: terminate ssh session with ~. kill parent sshd process kill parent bash process in all cases, the shell process just disappears immediately.
[16 Apr 2018 17:37]
Kenny Gryp
@Alfredo: Yeah that doesn't work. I tried that too. Nothing was happening on the shell as far as I know. The only thing possible is that is might have been waiting on user input (like a password)
[17 Apr 2018 15:12]
MySQL Verification Team
Hi, I tried everything I can think of (including running in vm and suspending vm's, running on real hw and killing the network physically, running on vm using double switch killing the middle one so that physically network exist but data is not going trough ...) and I can't reproduce this, so this might be some fluke on your system at the time and not a bug. If you reproduce this again please remember what you did :D thanks Bogdan