GNU bug report logs - #39164
27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems

Previous Next

Package: emacs;

Reported by: Justin Guenther <jguenther <at> gmail.com>

Date: Fri, 17 Jan 2020 19:02:01 UTC

Severity: normal

Merged with 40023, 40555

Found in versions 27.0.60, 26.3, 27.0.90

Fixed in version 27.1

Done: Robert Pluim <rpluim <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>
Cc: tomekowal <at> gmail.com, 39164 <at> debbugs.gnu.org, rpluim <at> gmail.com, jguenther <at> gmail.com
Subject: bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems
Date: Thu, 30 Jan 2020 16:49:48 +0200

> Date: Thu, 30 Jan 2020 18:42:41 +0900
> From: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>
> Cc: bug-gnu-emacs <at> gnu.org,
> 	tomekowal <at> gmail.com,
> 	rpluim <at> gmail.com,
> 	39164 <at> debbugs.gnu.org,
> 	jguenther <at> gmail.com
> 
> > My point is that having this code in the same place for all platforms is better for long-range maintenance.
> 
> If we make dummy calls before setrlimit in init_process_emacs, then an
> artificially increased limit is recorded to the variable nofile_limit,
> and that will be used in restore_nofile_limit later.

That's true, but restore_nofile_limit is called after the fork in the
context of the child process, so can that call cause any harm?

If it does do harm, maybe we should simply avoid that call on macOS?
This bug report was last modified 5 years and 35 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.