Switching to a Virtual Terminal "Freezes" Applications

Not sure if this is an issue with the xserver or amdgpu, or if it's an issue at all or by design, but since the "AIGLX: Suspending AIGLX clients for VT switch\n" is in 'glx/glxdri2.c' that is included in xorg-server, I'll start here.

Also not sure if AIGLX is even related in any way, but I am pretty sure I confirmed that I did not see it when using NVIDIA, and when I switched to AMD (xf86-video-amdgpu) is when I noticed that some applications stop doing their thing in the background when I switch to a virtual terminal, and there is this message which is currently my only lead.

On my Gentoo Linux installs I tend to make use of virtual terminals pretty often, and since I use no display managers and such, it's also the way to log in as another user to run their own X session. Likewise, there is no systemd, polkit, pam, and other such things that might commonly be found in many Linux systems nowadays.

Desktop is LXQt with KWin (sometimes LXQt and LXQt or Xfce on another user).

Some examples I've seen:

• Playing a video of a live stream (for example from twitch.tv) via mpv/streamlink; the video will go in the background for a time, but will eventually stop as if the network activity would stop.
• Online video games /may/ get disconnected (this /might/ not happen if the application is minimised before the VT switch (game running via Wine in this case)).
• The Gentoo Portage package manager gets stuck (I believe it was while fetching packages).
• When switching back to the desktop, instant messaging application qTox plays the notification sound for messages that came in during the VT switch (it does seem like the messages are actually delivered, however).

It somewhat seems like the applications actually hang, and as such, stop dealing with anything network-related and get disconnected, but some applications (like qTox, Irssi, Weechat) do stay connected. In the Gentoo Portage case, it's a CLI running in a terminal emulator (Konsole).

I may have seen this just by using 'ping' even, but testing it now, it does seem to keep going in the background.

I suppose it's more secure in that audio and such don't "bleed over" to the other user(s), but it certainly doesn't seem intentional that some things quite literally stop doing what they're supposed to be doing. : )

Thank you!