From: Eli Zaretskii <eliz@gnu.org>
To: Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs crashes when writting JavaScript
Date: Wed, 18 Sep 2019 15:18:45 +0300 [thread overview]
Message-ID: <83k1a5vlui.fsf@gnu.org> (raw)
In-Reply-To: <87v9tqcd57.fsf@yahoo.com.mx> (message from Jorge Javier Araya Navarro on Wed, 18 Sep 2019 00:49:24 -0600)
> From: Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx>
> Date: Wed, 18 Sep 2019 00:49:24 -0600
>
> I'm using Emacs 27.x compiled from the master branch. I have noticed that after several hours of
> work Emacs tends to crash or complete freeze the entire OS when I work on JavaScript code. I have
> prettier-js which prettifies the source after saving the file to disk, but not sure if this could be
> related. I also have suspicions on the parser of JS code, but because I have no idea how or where it
> keeps the AST, I can't be sure if that is related to the crashes too, I come to notice that under
> some circumstances –when the JSX code is fairly large and complex– Emacs slows down and feels heavy
> sort-of-speak.
>
> I would like to know if there is a way to monitor Emacs on a normal run and after it crashes get
> back something that can help debugging whatever the issue happens to be. This behavior has become
> recurrent during this month, IIRC.
Run Emacs under GDB, and when it crashes, produce a C-level backtrace
and report it with all the details to the bug tracker (M-x report-emacs-bug).
Thanks.
next prev parent reply other threads:[~2019-09-18 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v9tqcd57.fsf.ref@yahoo.com.mx>
2019-09-18 6:49 ` Emacs crashes when writting JavaScript Jorge Javier Araya Navarro
2019-09-18 12:18 ` Eli Zaretskii [this message]
2019-09-23 0:50 ` Jackson Ray Hamilton
2019-09-23 13:29 ` Dmitry Gutov
2019-09-23 18:12 ` [SPAM UNSURE] " Stephen Leake
2019-09-23 18:30 ` Jorge Javier Araya Navarro
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=83k1a5vlui.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jorgejavieran@yahoo.com.mx \
/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.