From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, Paul Eggert <eggert@cs.ucla.edu>,
60220@debbugs.gnu.org
Subject: bug#60220: 29.0.60; macOS 13.1 crash shortly after starting Emacs
Date: Fri, 30 Dec 2022 08:36:25 -0500 [thread overview]
Message-ID: <CAHyO48xBwVwp+ojijeAx8yO3FM5o1F4b_5cq3QKi_wSjq7ba1g@mail.gmail.com> (raw)
In-Reply-To: <83fscx70em.fsf@gnu.org>
On Fri, Dec 30, 2022 at 3:37 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Thu, 29 Dec 2022 17:16:18 -0800
> > Cc: Eli Zaretskii <eliz@gnu.org>, gerd.moellmann@gmail.com,
> > 60220@debbugs.gnu.org
> > From: Paul Eggert <eggert@cs.ucla.edu>
> >
> > On 12/29/22 16:03, Aaron Jensen wrote:
> > > Would it make sense to use block_atimers while loading native lisp? If
> >
> > Might, but it might make more sense not to be dynamically loading code
> > during an idle timer.
>
> This is a limitation we don't want, as it is too severe. How can we
> prevent loading when idle timers can run any Lisp, and an arbitrary
> Lisp program can always call some autoloaded function?
>
> And I don't understand why we'd want to have such a restriction, since
> idle timers run from the main loop, thus in safe context. It would be
> a gratuitous restriction that will only draw (justified) complaints.
>
> Can you explain why you think loading shared libraries from an Emacs
> idle timer could be dangerous? I don't think I understand that.
I've already disproven this. I can reproduce a crash with just an
after-init hook loading several features.
Aaron
next prev parent reply other threads:[~2022-12-30 13:36 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 15:11 bug#60220: 29.0.60; macOS 13.1 crash shortly after starting Emacs Aaron Jensen
2022-12-20 15:25 ` Aaron Jensen
2022-12-20 15:41 ` Eli Zaretskii
2022-12-20 15:59 ` Aaron Jensen
2022-12-20 17:23 ` Eli Zaretskii
2022-12-21 3:47 ` Aaron Jensen
2022-12-21 12:22 ` Eli Zaretskii
2022-12-21 13:29 ` Gerd Möllmann
2022-12-22 5:09 ` Aaron Jensen
2022-12-22 5:12 ` Aaron Jensen
2022-12-22 5:36 ` Gerd Möllmann
2022-12-22 8:18 ` Eli Zaretskii
2022-12-23 2:05 ` Paul Eggert
2022-12-23 2:22 ` Aaron Jensen
2022-12-23 5:33 ` Gerd Möllmann
2022-12-23 5:56 ` Paul Eggert
2022-12-24 6:45 ` Aaron Jensen
2022-12-24 6:57 ` Eli Zaretskii
2022-12-24 7:03 ` Aaron Jensen
2022-12-24 8:25 ` Paul Eggert
2022-12-24 15:11 ` Aaron Jensen
2022-12-25 5:30 ` Gerd Möllmann
2022-12-25 19:30 ` Aaron Jensen
2022-12-25 19:59 ` Eli Zaretskii
2022-12-27 11:12 ` Aaron Jensen
2022-12-27 13:11 ` Eli Zaretskii
2022-12-29 22:47 ` Aaron Jensen
2022-12-29 23:46 ` Aaron Jensen
2022-12-29 23:49 ` Paul Eggert
2022-12-29 23:59 ` Aaron Jensen
2022-12-30 0:03 ` Aaron Jensen
2022-12-30 1:16 ` Paul Eggert
2022-12-30 1:20 ` Aaron Jensen
2022-12-30 2:11 ` Aaron Jensen
2022-12-30 3:54 ` Aaron Jensen
2022-12-30 4:24 ` Aaron Jensen
2022-12-30 4:25 ` Aaron Jensen
2022-12-30 7:41 ` Gerd Möllmann
2022-12-30 8:03 ` Aaron Jensen
2022-12-30 8:42 ` Gerd Möllmann
2022-12-30 13:37 ` Aaron Jensen
2022-12-30 13:52 ` Aaron Jensen
2022-12-30 14:24 ` Aaron Jensen
2022-12-30 15:27 ` Gerd Möllmann
2022-12-30 15:50 ` Aaron Jensen
2022-12-30 8:37 ` Eli Zaretskii
2022-12-30 13:36 ` Aaron Jensen [this message]
2022-12-30 14:18 ` Eli Zaretskii
2022-12-30 22:42 ` Paul Eggert
2022-12-31 6:33 ` Eli Zaretskii
2022-12-30 8:32 ` Eli Zaretskii
2023-01-04 15:51 ` Andrea Corallo
2023-01-04 16:58 ` Eli Zaretskii
2023-01-10 15:28 ` Andrea Corallo
2023-01-10 16:57 ` Eli Zaretskii
2023-01-10 22:59 ` Aaron Jensen
2023-01-12 11:01 ` Andrea Corallo
2023-01-14 16:23 ` Aaron Jensen
2022-12-30 0:08 ` Paul Eggert
2022-12-30 8:29 ` Eli Zaretskii
2022-12-22 8:05 ` Eli Zaretskii
2022-12-20 15:32 ` Eli Zaretskii
2022-12-20 15:36 ` Aaron Jensen
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=CAHyO48xBwVwp+ojijeAx8yO3FM5o1F4b_5cq3QKi_wSjq7ba1g@mail.gmail.com \
--to=aaronjensen@gmail.com \
--cc=60220@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@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).