From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
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: Thu, 30 Jan 2020 18:42:41 +0900 [thread overview]
Message-ID: <wl4kwdmga6.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <0A439FD3-D066-4D6B-B73D-CFCF78DB18FD@gnu.org>
On Wed, 29 Jan 2020 21:38:32 +0900,
Eli Zaretskii wrote:
>
> On January 29, 2020 1:09:16 PM GMT+02:00, Eli Zaretskii <eliz@gnu.org> wrote:
> > On January 29, 2020 12:26:23 PM GMT+02:00, YAMAMOTO Mitsuharu
> > <mituharu@math.s.chiba-u.ac.jp> wrote:
> > > On Wed, 29 Jan 2020 02:37:10 +0900,
> > > Eli Zaretskii wrote:
> > > >
> > > > > 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?
> > >
> > > The functions in question are used together with Mac-specific GUI
> > > event handing. I placed the dummy calls inside macOS-specific code
> > so
> > > the -nw case may not change the behavior from the original one.
> >
> > We could condition the code in process.c by the aporopriate NS
> > preprocessor condition to make it take effect only in GUI sessions.
>
> Sorry, preprocessor condition is not TRT, we should have a runtime test that limits these dummy calls to GUI sessions.
>
> 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.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2020-01-30 9:42 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wl4kwdmga6.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=39164@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jguenther@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.