Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emacs28 / flycheck is spawning wild running shellcheck processes eating up the system memory (oom-kill) #2014

Open
DirkSchmitt opened this issue Mar 29, 2023 · 0 comments

Comments

@DirkSchmitt
Copy link

Bug description

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))

System Configuration

As reported by dpkg -l:

ii elpa-flycheck 32~git.20200527.9c435db3-3 all modern on-the-fly syntax checking for Emacs
ii emacs 1:28.2+1-13 all GNU Emacs editor (metapackage)
ii shellcheck 0.9.0-1 amd64 lint tool for shell scripts

Also reported to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033655

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant