Bug 445411

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open a program with Wine that uses systray (Battle.net)
2. Turn off compositing
3. Let primary window lose focus

OBSERVED RESULT
xembedsniproxy jumps to high CPU usage and spams journal:

Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below
Nov 12 21:11:51 Arch-PC xembedsniproxy[6842]: Container window visible, stack below


EXPECTED RESULT
No jump in CPU usage, no log spam

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.14.15-210 & 5.23.3-1
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: qt5-base 5.15.2+kde+r254-1

ADDITIONAL INFORMATION
Same as previous report: https://invent.kde.org/plasma/plasma-workspace/-/issues/12