From: Kaushal Modi <kaushal.modi@gmail.com>
To: 29463@debbugs.gnu.org
Subject: bug#29463: Backtraces with large strings is very slow
Date: Tue, 28 Nov 2017 22:33:07 +0000 [thread overview]
Message-ID: <CAFyQvY093hG0Y2h4Dp3=CRTog_4K57WW30B91RJDp-O+upv1Bw@mail.gmail.com> (raw)
In-Reply-To: <m38tesh1p3.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
> I was trying to debug some code that dealt with very large SVG images,
and getting a backtrace buffer proved impossible -- Emacs would just
hang.
+1. Though I see that slow-down on backtrace on emacs-26 branch too..
especially when edebugging/debugging through code in an Org exporter.
Org exporters use an INFO plist that contains loads of information for the
whole Org buffer (which is common to be 1000's of lines). So each time the
edebug step comes to the info variable, it could few minutes for emacs
before I can move on to the next edebug step.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 768 bytes --]
next prev parent reply other threads:[~2017-11-28 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 2:53 bug#29463: 27.0.50; Backtraces with large strings is very slow Lars Ingebrigtsen
2017-11-28 22:33 ` Kaushal Modi [this message]
2017-11-29 1:48 ` bug#29463: " Noam Postavsky
2019-09-21 8:20 ` bug#29463: 27.0.50; " 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
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='CAFyQvY093hG0Y2h4Dp3=CRTog_4K57WW30B91RJDp-O+upv1Bw@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=29463@debbugs.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).