Open mclearc opened 5 years ago
Colin McLear notifications@github.com writes:
I've been seeing for awhile (maybe the past month or two) that async spawns many emacs processes over time like so:
/private/var/folders/g0/0j3_9c5d5xs81zh34_ng8mj80000gn/T/AppTranslocation/B57D43C2-CC68-4399-976F-97670E0825B7/d/Emacs.app/Contents/MacOS/Emacs-x86_64-10_10 -Q -l /Users/roambot/.emacs.d/.local/elpa/async-20181224.454/async.elc -batch -f async-batch-invoke
This is problematic because whenever I quit emacs I get asked about running processes, and more problematically, that when too many have spawned I get a "too many open files" message which effectively locks up emacs (e.g. I can't quit or run commands).
My setup is simply:
(use-package async :defer 10)
Any idea what the problem is? Is it related to #96 ? Thanks.
If you have any emacs async processes remaining, it is that these processes fail for some reasons and are still hanging around, verify that emacs-async is working properly (copy files etc...). Be sure as well that your emacs async doesn't ask for something (e.g. a password) in background, for this use auth-source to avoid beeing prompted in the batch process.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.*
-- Thierry
Async seems to work properly, except for these processes. I'm not even sure what is generating them. Is there a way to find this out other than bisecting my (very long) init file?
I've been seeing for awhile (maybe the past month or two) that async spawns many emacs processes over time like so:
This is problematic because whenever I quit emacs I get asked about running processes (see #8), and more problematically, that when too many have spawned I get a "too many open files" message which effectively locks up emacs (e.g. I can't quit or run commands).
My setup is simply:
Any idea what the problem is? Is it related to #96 ? Thanks.