Unexpected Behavior when closing a terminal running "sudo ping -f www.google.com" via the "x"

[hduwjg bjsksu]

I run "sudo ping -f www.google.com". I then closed the window by clicking the "X" and a random cpu core is pinned to 100%.

What I expected: after I close the windows, the command completely closes and shuts down

What actually happened: after I click the "X", the terminal window closes, but in ksysguard a running process called "ping" starts consuming cpu resources.

If I stop the command via "Control+C" and then close the window via the "X", this behavior is not present.

Xubuntu version: 20.04
xfce4-terminal version: 0.8.9.1-1

side note: this behavior is not present on Xubuntu Desktop 18.04 AMD64 live desktop

If you need anymore information about this problem please lay out the steps to get this info.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xfce4-terminal 0.8.9.1-1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: XFCE
Date: Mon Jun 22 18:47:01 2020
ExecutablePath: /usr/bin/xfce4-terminal
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: xfce4-terminal
UpgradeStatus: No upgrade log present (probably fresh install)