«Too many open files» in error log leads to a high CPU usage when display is put to sleep / turned off

[braindefender]

Describe the bug

When the computer is idle and the display is turned off, many errors of leftwm-worker are logged in the journalctl log.

This results in high CPU usage for both the systemd-journald and leftwm-worker processes.

When I click the mouse or press any key, the display turns back on and the errors disappear.

Expected behavior (optional)

No response

Steps to reproduce (optional)

Simply do nothing and let the pc put displays to sleep

Relevant log output (optional)

Dec 02 14:33:33 terra leftwm-worker[3269]: Accept failed = Os { code: 24, kind: Uncategorized, message: "Too many open files" }
Dec 02 14:33:33 terra leftwm-worker[3269]: Accept failed = Os { code: 24, kind: Uncategorized, message: "Too many open files" }
Dec 02 14:33:33 terra leftwm-worker[3269]: Accept failed = Os { code: 24, kind: Uncategorized, message: "Too many open files" }
Dec 02 14:33:33 terra leftwm-worker[3269]: Accept failed = Os { code: 24, kind: Uncategorized, message: "Too many open files" }
Dec 02 14:33:33 terra leftwm-worker[3269]: Accept failed = Os { code: 24, kind: Uncategorized, message: "Too many open files" }

OS / Distro

Linux terra 6.6.2 #1-NixOS SMP PREEMPT_DYNAMIC x86_64 GNU/Linux

Additional System Information (optional)

Using systemd, starting leftwm via `.xinitrc` with `exec dbus-launch leftwm`
Installed with pkgs.leftwm. Using picom-next.
Intel UHD video on i5-13600K. NVidia drivers are turned off and passed to vfio.

LeftWM Check

:: LeftWM version: 0.5.1
:: LeftWM git hash: unknown
:: Enabled features:  journald-log lefthk
:: Checking feature dependencies . . .
    -> journald-log OK
    -> lefthk OK
:: Checking for leftwm binaries . . .
    -> Binaries OK 
:: Loading configuration . . .
    -> Configuration loaded OK 
:: Checking keybinds . . .
    -> All keybinds OK
:: Checking environment . . .
    -> Environment OK 
:: Checking theme . . .
    -> Theme OK

[Eskaan]

Hey, sorry this took so long.

That this limit is reached usually means that some other program has opened the file this many times (and didn't close them after).
A typical example for this would be a bar or similar, so what exactly are you using as your theme?

It's presumably kind of a duplicate of #903 with the error lying somewhere else.