unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jeremy Bryant via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 71367@debbugs.gnu.org, "João Távora" <joaotavora@gmail.com>
Subject: bug#71367: 30.0.50; ELPA package breadcrumb causes Emacs freeze when editing json file
Date: Fri, 07 Jun 2024 22:23:36 +0100	[thread overview]
Message-ID: <878qzg8n1j.fsf@jeremybryant.net> (raw)
In-Reply-To: <87tti8binx.fsf@fastmail.fm> (Tassilo Horn's message of "Tue, 04 Jun 2024 21:40:50 +0200")

Tassilo Horn <tsdh@gnu.org> writes:

> I use and like the breadcrumb ELPA package.
>
>   https://elpa.gnu.org/packages/breadcrumb.html
>
> It's installed/enabled using:
>
> --8<---------------cut here---------------start------------->8---
> (use-package breadcrumb
>   :ensure t
>   :init (breadcrumb-mode 1))
> --8<---------------cut here---------------end--------------->8---
>
> Now when I find the attached mirrorstatus.json using json-ts-mode (that
> seems to be important), set point on the first { and insert some spaces,
> Emacs will eventually freeze for several seconds or even minutes.
>
> It can be reproduced with
>
>   emacs -Q
>   M-x package-initialize RET
>   M-: (package-activate 'breadcrumb) RET
>   M-x breadcrumb-mode RET
>
> and then finding the file and doing as written above.
>
> I've also attached a gdb backtrace which suggests that emacs is
> collecting garbage (produced by the breadcrumb ELN code)?  I've also
> tried profiler-start, reproduce the freeze, wait for it to go away,
> profiler-report.  That said that 99% of cpu time where spent in
> Automatic GC.
>
> I currently have no emacs without native compilation handy so I cannot
> tell if that's important, too.  Can I somehow tell emacs not to compile
> breadcrumb natively after deleting the eln file?
>
> [2. application/gzip; mirrorstatus.json.gz]...
>
> [3. application/gzip; backtrace.txt.gz]...
>

João is the maintainer, CC'd





      parent reply	other threads:[~2024-06-07 21:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 19:40 bug#71367: 30.0.50; ELPA package breadcrumb causes Emacs freeze when editing json file Tassilo Horn
2024-06-04 20:49 ` Andrea Corallo
2024-06-05  7:24   ` Tassilo Horn
2024-06-05  9:36     ` Andrea Corallo
2024-06-06  9:35       ` Eli Zaretskii
2024-06-06 10:07         ` João Távora
2024-06-06 11:33           ` Eli Zaretskii
2024-06-06 11:47             ` João Távora
2024-06-06 12:08               ` Eli Zaretskii
2024-06-06 13:00                 ` João Távora
2024-06-06 13:37                   ` Eli Zaretskii
2024-06-06 14:01                     ` João Távora
2024-06-06 14:29                       ` Tassilo Horn
2024-06-07 21:23 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=878qzg8n1j.fsf@jeremybryant.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71367@debbugs.gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=joaotavora@gmail.com \
    --cc=tsdh@gnu.org \
    /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).