Package: elpa-flycheck Version: 32~git.20200527.9c435db3-3 Severity: grave X-Debbugs-Cc: none, H.-Dirk Schmitt <d...@computer42.org>
The combination of Emacs28 + elpa-flycheck + shellcheck in *bookworm* spawn never terminating shellcheck processes. These are eating up the memory and trigger oom-kill. **This renders my system unstable.** It appears to be blocked minutes till the oem-kill cleans up some memory. Analysis: I have temporarly downgraded elpa-flycheck and shellcheck. The wild processes are still spawned. So I assume that Emacs28 introduce a different behaviour here that is probematic for flycheck or shellcheck. Mitigation: As a mitigation I exclude the invocation of shellcheck in my Emacs setup: `(customize-set-variable 'flycheck-disabled-checkers '(sh-shellcheck))` Suggestion: I suggest to add this mitigation temporarily to the elpa-flycheck package to avoid degraded systems untill a real solution is found. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (600, 'testing-security'), (600, 'testing'), (500, 'stable-security'), (99, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de:en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages elpa-flycheck depends on: ii dh-elpa-helper 2.0.16 ii elpa-dash 2.19.1+git20220608.1.0ac1ecf+dfsg-1 ii elpa-let-alist 1.0.6-2 ii elpa-pkg-info 0.6-6 ii elpa-seq 2.23-1 ii emacs 1:28.2+1-13 ii emacs-gtk [emacs] 1:28.2+1-13 ii emacsen-common 3.0.5 Versions of packages elpa-flycheck recommends: ii emacs 1:28.2+1-13 ii emacs-gtk [emacs] 1:28.2+1-13 Versions of packages elpa-flycheck suggests: pn flycheck-doc <none> -- no debconf information
