Bad X11 behavior (message flood?) making tint2 unresponsive

[abique]

Hi,

Starting my X11 slint app makes tint2 unresponsive.
Everything becomes super slow to react, when clicking on tint2 to switch desktop / app.
I can confirm the issue with Openbox. I haven't tried other WM.

I suspect that the slint app is doing incorrect communication with the X server, possibly flooding or making some properties extremely large and hard to work with.

I've got this setup for maybe 10 years and it is the first time I see this.

slint = { version = "1.5.1", default-features = false, features = [
    "compat-1-2",
    "std",
    "backend-winit",
    "backend-winit-wayland",
    "backend-winit-x11",
    "renderer-skia",
] }

[abique]

Checking with xev, it is flooding messages like crazy:

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x27 (WM_NAME), time 46067589, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x15a (_NET_WM_NAME), time 46067589, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x143 (_MOTIF_WM_HINTS), time 46067589, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x166 (_NET_WM_ALLOWED_ACTIONS), time 46067589, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x163 (_NET_WM_ICON), time 46067604, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x15b (_NET_WM_VISIBLE_NAME), time 46067604, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x15d (_NET_WM_VISIBLE_ICON_NAME), time 46067605, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x166 (_NET_WM_ALLOWED_ACTIONS), time 46067605, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x163 (_NET_WM_ICON), time 46067625, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x27 (WM_NAME), time 46067625, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x15a (_NET_WM_NAME), time 46067625, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x143 (_MOTIF_WM_HINTS), time 46067625, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x163 (_NET_WM_ICON), time 46067637, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x15b (_NET_WM_VISIBLE_NAME), time 46067637, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x163 (_NET_WM_ICON), time 46067641, state PropertyNewValue

PropertyNotify event, serial 25, synthetic NO, window 0x3a00003,
    atom 0x27 (WM_NAME), time 46067641, state PropertyNewValue

There's an infinite loop somewhere, and it is burning my CPU...

[tronical]

I've tried to reproduce this, but I haven't had any luck. Running openbox and tint2 as task manager, starting the slint gallery (with renderer-skia and backend-winit).

Do you know of any way that we could try to reproduce this?

(FWIW, we don't really do anything specifically x11 related, but perhaps our usage of winit triggers something)

[tronical]

I debugged a bit with @abique and at least in his case it wasn't related to x11 messages but rather than the application was constantly repainting even when not visible on the screen.

[tronical]

I've created #5050 to track this in line with macOS. Best workaround for now is to use Wayland instead (but I understand, that doesn't come with open box :)