Weird. netin was busy, yet the bottom of the screen implies more outbound traffic (I guess it's connected the other way around?)
And the log looks like a SMB/CIFS issue... maybe not the interweb?
But, it definitely looks like something got stuck in a loop and triggered a memory leak.
Whatever VM / CT was using CPUs 7 & 10 at the time was the problem... find that and you'll find the next step down the rabbit hole...
It looks like it was a Plex scan that tied it's self up in knots and locked up the SMB share and it just happened that it was the QBT container that I noticed it on first.
Some of the logs did mention Plex was soft locked as well.
