unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: tomekowal@gmail.com, rpluim@gmail.com, 39164@debbugs.gnu.org,
	jguenther@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	[thread overview]
Message-ID: <83a767o52x.fsf@gnu.org> (raw)
In-Reply-To: <wlmua7zyi6.wl-mituharu@math.s.chiba-u.ac.jp> (message from YAMAMOTO Mitsuharu on Tue, 28 Jan 2020 19:06:09 +0900)

> Date: Tue, 28 Jan 2020 19:06:09 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: Robert Pluim <rpluim@gmail.com>,
> 	tomekowal@gmail.com,
> 	39164@debbugs.gnu.org,
> 	jguenther@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.





  reply	other threads:[~2020-01-28 17:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 19:00 bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems Justin Guenther
2020-01-17 21:01 ` Eli Zaretskii
2020-01-20  9:15   ` Robert Pluim
2020-01-20 18:00     ` Eli Zaretskii
2020-01-20 18:42       ` Robert Pluim
2020-01-27 13:26         ` mituharu
2020-01-27 18:19           ` Eli Zaretskii
2020-01-28  7:59             ` Robert Pluim
2020-01-28  8:23               ` YAMAMOTO Mitsuharu
2020-01-28  8:41                 ` Robert Pluim
2020-01-28  9:02                 ` Eli Zaretskii
2020-01-28  9:14                   ` YAMAMOTO Mitsuharu
2020-01-28  9:42                     ` Eli Zaretskii
2020-01-28 10:06                       ` YAMAMOTO Mitsuharu
2020-01-28 17:37                         ` Eli Zaretskii [this message]
2020-01-29 10:26                           ` YAMAMOTO Mitsuharu
2020-01-29 11:09                             ` Eli Zaretskii
2020-01-29 12:38                               ` Eli Zaretskii
2020-01-30  9:42                                 ` YAMAMOTO Mitsuharu
2020-01-30 14:49                                   ` Eli Zaretskii
2020-01-26 17:41 ` bug#39164: Reproducing SIGSEGV bug Tomasz Kowal

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=83a767o52x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39164@debbugs.gnu.org \
    --cc=jguenther@gmail.com \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    --cc=rpluim@gmail.com \
    --cc=tomekowal@gmail.com \
    /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).