Processing control commands:
> tag -1 unreproducible
Bug #1033655 [elpa-flycheck] elpa-flycheck: Emacs28 / flycheck is spawning wild
running shellcheck processes eating up the system memory (oom-kill)
Ignoring request to alter tags of bug #1033655 to the same tags previously set
> severity -1 imp
Processing control commands:
> tag -1 unreproducible
Bug #1033655 [elpa-flycheck] elpa-flycheck: Emacs28 / flycheck is spawning wild
running shellcheck processes eating up the system memory (oom-kill)
Added tag(s) unreproducible.
> severity -1 important
Bug #1033655 [elpa-flycheck] elpa-flycheck:
Control: tag -1 unreproducible
Control: severity -1 important
H.-Dirk Schmitt writes:
> Package: elpa-flycheck
> Version: 32~git.20200527.9c435db3-3
> Severity: grave
> X-Debbugs-Cc: none, H.-Dirk Schmitt
>
>
> The combination of Emacs28 + elpa-flycheck + shellcheck in *bookworm*
> spawn neve
For myself I have deinstalled elpa-org for the moment.
But this mitigation – or the suggested changing of the load-path –
introducing unnecessary modifications, which will – Murphy's Law – become
persistent.
A „clean solution“ should avoid duplicated distribution of the same
functionality – esp
I also reported the Issue to the upstream project:
https://github.com/flycheck/flycheck/issues/2014
Package: elpa-flycheck
Version: 32~git.20200527.9c435db3-3
Severity: grave
X-Debbugs-Cc: none, H.-Dirk Schmitt
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
6 matches
Mail list logo