From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22814@debbugs.gnu.org, andlind@gmail.com
Subject: bug#22814: 25.0.91; Emacs runs out of file descriptors on OS X
Date: Sat, 27 Feb 2016 20:51:27 +0100 [thread overview]
Message-ID: <87vb5alyo0.fsf@gmx.de> (raw)
In-Reply-To: <83h9guaqov.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Feb 2016 21:39:12 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> I meant that maybe a similar internal limit could be added, in order to
>> keep Emacs running normal, not being at its upper limits.
>
> It's not a fixed limit, alas. The number of threads we can start is
> limited by available memory (because each thread uses some for its
> stack), and the amount of available memory depends on how much Emacs
> itself uses.
In this case one could use a hard-coded limit. 512 watches, that's it.
>> > How about defaulting to auto-revert-use-notify = nil when
>> > global-auto-revert-mode is turned on?
>>
>> I don't know whether it is the majority of users, who enable
>> global-auto-revert-mode *and* work with hundreds of buffers. So far,
>> there is one report about.
>>
>> And such power users are more likely to know how to disable file
>> notification then.
>
> Perhaps we shouldn't wait for a flood of bug reports, and do this
> proactively?
I've explained my plans how to protect the libraries, using an internal
limit. This shall avoid such a flood of bug reports.
And if the changes are small enough (likely they are), they could go
even into the emacs-25 branch.
Bst regards, Michael.
next prev parent reply other threads:[~2016-02-27 19:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 6:18 bug#22814: 25.0.91; Emacs runs out of file descriptors on OS X David Caldwell
2016-02-26 8:34 ` Michael Albinus
2016-02-26 9:05 ` David Caldwell
2016-02-26 10:26 ` Nicolas Richard
2016-02-26 9:22 ` Eli Zaretskii
2016-02-26 20:05 ` Michael Albinus
2016-02-26 9:04 ` Eli Zaretskii
2016-02-26 20:51 ` Anders Lindgren
2016-02-27 8:00 ` Michael Albinus
2016-02-27 9:19 ` Eli Zaretskii
2016-02-27 13:26 ` Michael Albinus
2016-02-27 19:00 ` Anders Lindgren
2016-02-27 19:12 ` Michael Albinus
2016-02-27 19:17 ` Eli Zaretskii
2016-02-27 19:33 ` Michael Albinus
2016-02-27 19:39 ` Eli Zaretskii
2016-02-27 19:51 ` Michael Albinus [this message]
2016-02-27 19:58 ` Eli Zaretskii
2016-02-27 20:06 ` Michael Albinus
2016-02-27 20:25 ` Eli Zaretskii
2016-02-28 9:57 ` Michael Albinus
2016-02-28 15:51 ` Eli Zaretskii
2016-02-27 19:14 ` Eli Zaretskii
2016-02-27 19:26 ` Michael Albinus
2016-02-27 19:36 ` Eli Zaretskii
2016-02-27 19:39 ` Michael Albinus
2016-02-27 19:56 ` Michael Albinus
2016-02-27 20:06 ` Eli Zaretskii
2016-02-29 10:24 ` Michael Albinus
2016-02-29 16:02 ` Eli Zaretskii
2016-03-02 15:03 ` Michael Albinus
2016-03-02 16:01 ` Eli Zaretskii
2016-03-04 7:53 ` Michael Albinus
2016-03-04 8:14 ` John Wiegley
2016-03-04 8:29 ` Eli Zaretskii
2016-03-04 14:05 ` Michael Albinus
2016-03-04 14:11 ` Michael Albinus
2016-04-10 8:21 ` Michael Albinus
2016-04-10 20:37 ` Anders Lindgren
2016-04-11 6:40 ` Michael Albinus
2016-04-11 6:48 ` Anders Lindgren
2016-04-11 6:58 ` Michael Albinus
2016-04-11 18:59 ` Anders Lindgren
2016-04-12 7:44 ` Michael Albinus
2016-02-27 9:55 ` Anders Lindgren
2016-02-27 10:46 ` Eli Zaretskii
2016-02-27 11:38 ` Anders Lindgren
2016-02-27 12:17 ` Michael Albinus
2016-02-27 12:40 ` Eli Zaretskii
2016-02-27 12:49 ` Michael Albinus
2016-02-27 12:52 ` Eli Zaretskii
2016-02-27 13:00 ` Michael Albinus
2016-03-05 0:32 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb5alyo0.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=22814@debbugs.gnu.org \
--cc=andlind@gmail.com \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).