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, rpluim <at> gmail.com, 39164 <at> debbugs.gnu.org, jguenther <at> gmail.com
Subject: bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems
Date: Tue, 28 Jan 2020 19:37:10 +0200

> Date: Tue, 28 Jan 2020 19:06:09 +0900
> From: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>
> Cc: Robert Pluim <rpluim <at> gmail.com>,
> 	tomekowal <at> gmail.com,
> 	39164 <at> debbugs.gnu.org,
> 	jguenther <at> gmail.com
> 
> The increase happens only once per function in question.  So we make a
> dummy call in advance so later calls may not cause the increase in
> unpredicable timings.

Can these dummy calls be made just before we call setrlimit in
init_process_emacs, as opposed to in a macOS-specific source file?

Also, could there be Core Foundation functions other than those you
propose to call, that have the same effect?  IOW, how can we be sure
we issued a dummy call for every such function that matters to Emacs?

Thanks.
This bug report was last modified 5 years and 34 days ago.

Previous Next

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