all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Reingruber, Richard" <richard.reingruber@sap.com>
Cc: 53348@debbugs.gnu.org
Subject: bug#53348: 27.2; Crash in mark_object
Date: Tue, 18 Jan 2022 18:53:20 +0200	[thread overview]
Message-ID: <83bl09ugsf.fsf@gnu.org> (raw)
In-Reply-To: <7867C7DB-C88C-4DC8-9315-8C987DFB9DFA@sap.com> (bug-gnu-emacs@gnu.org)

> Date: Tue, 18 Jan 2022 08:35:10 +0000
> From:  "Reingruber, Richard" via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I've got a new Apple M1 Pro macbook. I'm experiencing crashes with Emacs 27.2 which I installed using homebrew.
> 
> The information below was generated after I restarted Emacs following a crash.
> 
> I added the crash report from macos because I could not find a report from emacs.
> 
> Looks like a GC crash in mark_object.
> 
> Unfortunately I cannot reproduce the crash. This is the first crash report I
> got. Normally Emacs just hangs. I sampled the process using macos activity
> monitor and found a similar stack as in the crash.

Looks like C stack overflow, or at least a possibility of it (you
didn't show all of the backtrace levels, so it's hard to be sure).

Can you configure your environment, or rebuild Emacs, so that the
amount of stack space available to it is larger?





  reply	other threads:[~2022-01-18 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  8:35 bug#53348: 27.2; Crash in mark_object Reingruber, Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-18 16:53 ` Eli Zaretskii [this message]
2022-01-18 17:07   ` Reingruber, Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-18 17:49     ` Eli Zaretskii
2022-01-21 10:34       ` Lars Ingebrigtsen
2022-01-21 10:36         ` Lars Ingebrigtsen

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=83bl09ugsf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53348@debbugs.gnu.org \
    --cc=richard.reingruber@sap.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.