|Subject:||bug#22814: 25.0.91; Emacs runs out of file descriptors on OS X|
|Date:||Sat, 27 Feb 2016 20:00:30 +0100|
Eli Zaretskii <address@hidden> writes:
>> > One simple way to handle this is to define a variable with "max"
>> > number of files the notification system can handle. We can set this
>> > to, say, 200 on OS X and unlimited on other systems.
>> Would be possible, yes. I would prefer to set the limit to a system
>> related value. Does there exist a portable way to detect, how many file
>> descriptors / processes Emacs is able to consume?
> Not portably, AFAIK.
On POSIX systems, we could propagate the result of
if !(getrlimit (RLIMIT_NOFILE, &rlim))
return make_number (rlim.rlim_cur);
Maybe we add a function like `<library>-max-descriptors' to the
libraries. Or maybe not, and the backends check this themselves, and
cease to work when reaching an internal limit. Such an internal limit
could be half the number of soft RLIMIT_NOFILE on POSIX systems, for
> Also, different implementations use different
> resources for receiving file notifications. For example, w32notify
> uses one handle and one thread per watched file/directory. The number
> of handles a process can have on Windows is very large, and the
> theoretical max number of threads is 32K, but both are limited by the
> resources already consumed by the Emacs process. So determining the
> practical maximum at any given point will require a non-trivial
There must be different scenarios for different file notification
libraries. But using RLIMIT_NOFILE as basis when possible gives us
better results on systems like OS X and FreeBSD, which both use kqueue,
but provide different ressource limits.
Best regards, Michael.
|[Prev in Thread]||Current Thread||[Next in Thread]|