From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Phillip Hutchings <phillip@iontech.nz>
Cc: 38618@debbugs.gnu.org
Subject: bug#38618: 27.0.50; Mach port leak on macOS Catalina causing crash
Date: Tue, 17 Dec 2019 12:49:07 +0900 [thread overview]
Message-ID: <wld0cnipcc.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <0DAC0841-F55E-48B8-8007-39107F92C039@iontech.nz>
On Sun, 15 Dec 2019 10:35:10 +0900,
Phillip Hutchings wrote:
>
> On macOS Catalina (all versions up to and including 10.15.2), after
> opening a file stored on an iCloud Drive folder Emacs leaks Mach ports
> eventually resulting in an Emacs crash during a random syscall.
>
> Reproduction:
> * Using Emacs for MacOS X (currently using Nightly build, but also on
> the 26.3 release from 2019-09-02
> * Open a file stored in an iCloud Drive folder, eg Documents when using
> default settings
> * Modify the file, no need to save it, only modify the contents
> * Emacs will leak Mach ports on every edit.
>
> This does not happen on non-iCloud Drive files, the port count observed
> in Activity Monitor does not change for these files.
The Mac port (not the NS port in your report) also has the problem of
Mach port leaks in -[NSWindow setRepresentedURL:] on macOS 10.15. I
think this is a bug in AppKit or some lower-level stuff. I'll file it
to Apple later.
I've installed a workaround into the "work" branch of the repository
of the Mac port:
https://bitbucket.org/mituharu/emacs-mac/commits/19c97087065b7ca64b71f392a453673042e024c6
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2019-12-17 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 1:35 bug#38618: 27.0.50; Mach port leak on macOS Catalina causing crash Phillip Hutchings
2019-12-15 14:48 ` Alan Third
2019-12-16 4:01 ` Phillip Hutchings
2019-12-17 3:49 ` YAMAMOTO Mitsuharu [this message]
2019-12-17 21:23 ` Alan Third
2019-12-17 21:29 ` Phillip Hutchings
2019-12-22 11:49 ` Alan Third
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=wld0cnipcc.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=38618@debbugs.gnu.org \
--cc=phillip@iontech.nz \
/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.