From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30364@debbugs.gnu.org, alan@idiocy.org, npostavs@gmail.com,
npostavs@users.sourceforge.net
Subject: bug#30364: 26.0.91; thread crash on macos
Date: Sun, 18 Feb 2018 21:32:14 +0200 [thread overview]
Message-ID: <83o9km9jr5.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48ztiUhWrSdswr3tgq5KKOP_p8CsdavTYAtqnfTLR7o0VA@mail.gmail.com> (message from Aaron Jensen on Sun, 18 Feb 2018 10:59:02 -0800)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Sun, 18 Feb 2018 10:59:02 -0800
> Cc: Noam Postavsky <npostavs@gmail.com>, 30364@debbugs.gnu.org,
> Noam Postavsky <npostavs@users.sourceforge.net>, Alan Third <alan@idiocy.org>
>
> Out of curiosity, would it be possible to limit GCs to only happen on
> the main thread? They're stop the world any way, right, so does it
> matter which thread they happen on?
A thread that runs Lisp can continue running Lisp for a long time, and
will generate a lot of garbage. If GC is prevented, we will risk
running out of memory.
IOW, leaving GC for the main thread only makes sense if we can be sure
the main thread will run shortly. But that cannot be guaranteed with
the current thread model, where a thread must exit or yield before
another thread can run.
next prev parent reply other threads:[~2018-02-18 19:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 8:21 bug#30364: 26.0.91; thread crash on macos Aaron Jensen
2018-02-14 1:05 ` Noam Postavsky
2018-02-14 1:22 ` Aaron Jensen
2018-02-17 14:44 ` Noam Postavsky
2018-02-17 17:58 ` Aaron Jensen
2018-02-17 18:17 ` Eli Zaretskii
2018-02-17 18:40 ` Aaron Jensen
2018-02-17 18:55 ` Eli Zaretskii
2018-02-18 1:58 ` Aaron Jensen
2018-02-18 4:51 ` Eli Zaretskii
2018-02-18 4:54 ` Aaron Jensen
2018-02-18 16:45 ` Eli Zaretskii
[not found] ` <CAHyO48y+c21biWxQDTMvW2PkSKW6TzZVWQ94yUPN_4n3utDv5A@mail.gmail.com>
2018-02-18 18:25 ` Eli Zaretskii
2018-02-18 18:38 ` Aaron Jensen
2018-02-18 18:39 ` Aaron Jensen
2018-02-18 18:59 ` Aaron Jensen
2018-02-18 19:32 ` Eli Zaretskii [this message]
2018-02-18 19:49 ` Aaron Jensen
2018-02-18 20:15 ` Eli Zaretskii
2018-02-18 21:12 ` Aaron Jensen
2018-02-19 3:29 ` Eli Zaretskii
2018-02-19 17:24 ` Paul Eggert
2018-02-19 17:29 ` Daniel Colascione
2018-02-19 18:39 ` Eli Zaretskii
2018-02-19 18:33 ` Eli Zaretskii
2018-02-19 18:47 ` Aaron Jensen
2018-02-19 20:08 ` Paul Eggert
2018-02-19 20:16 ` Aaron Jensen
2018-02-25 20:52 ` Aaron Jensen
2018-02-27 17:30 ` Paul Eggert
2018-02-27 17:38 ` Aaron Jensen
2018-02-27 17:44 ` Paul Eggert
2018-02-28 5:33 ` Aaron Jensen
2018-02-28 15:33 ` Eli Zaretskii
2018-02-28 15:35 ` Aaron Jensen
2018-02-28 16:20 ` Eli Zaretskii
2018-02-28 17:32 ` Aaron Jensen
2018-02-28 17:38 ` Eli Zaretskii
2018-02-28 17:59 ` Aaron Jensen
2018-02-28 18:07 ` Aaron Jensen
2018-02-28 19:15 ` Paul Eggert
2018-02-28 20:36 ` Eli Zaretskii
2018-03-01 0:31 ` Paul Eggert
2018-03-01 8:37 ` Aaron Jensen
2018-05-13 15:13 ` Noam Postavsky
2018-05-13 16:26 ` Eli Zaretskii
2018-05-14 20:03 ` Paul Eggert
2018-02-28 16:19 ` Paul Eggert
2018-02-18 19:07 ` Eli Zaretskii
2018-02-18 19:04 ` Eli Zaretskii
2018-02-18 11:01 ` Alan Third
2018-02-17 18:23 ` 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
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=83o9km9jr5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30364@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=alan@idiocy.org \
--cc=npostavs@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).