From: Ihor Radchenko <yantar92@gmail.com>
To: Luca Ferrari <fluca1978@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: emacs really slow when inserting a new source code block
Date: Tue, 27 Sep 2022 21:23:19 +0800 [thread overview]
Message-ID: <87h70tgddk.fsf@localhost> (raw)
In-Reply-To: <CAKoxK+6WTAnL6y4mUAMPBCcpPoz0hrXJMZo5x1ccj0ySPe6reA@mail.gmail.com>
Luca Ferrari <fluca1978@gmail.com> writes:
> On Mon, Sep 26, 2022 at 5:16 PM Ihor Radchenko <yantar92@gmail.com> wrote:
>> I think you tried to use M-x profiler-stop instead of M-x profiler-report
>> M-x profiler-report show yield a new buffer displayed the profiler tree.
>> M-x profiler-write-profile will work from inside that buffer.
>
> I was careful to do the steps in the right order, and my message
> buffer tells the profiler has been stopped after the write profiler
> fails:
> ...
> profiler-write-profile: Wrong type argument: arrayp, nil
> CPU and memory profiler stopped
> Reverted buffer
This is strange.
Did nothing happen after M-x profiler-report?
Can you try again and check if *CPU-Profiler-Report ...* buffer exists
in Emacs (... will be current date and time)?
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-09-27 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 17:35 emacs really slow when inserting a new source code block Luca Ferrari
2022-09-26 4:42 ` Ihor Radchenko
2022-09-26 15:07 ` Luca Ferrari
2022-09-26 15:17 ` Ihor Radchenko
2022-09-27 12:42 ` Luca Ferrari
2022-09-27 13:23 ` Ihor Radchenko [this message]
2022-09-28 12:55 ` Luca Ferrari
2022-09-28 13:16 ` Ihor Radchenko
2022-09-28 14:15 ` Luca Ferrari
2022-09-28 14:21 ` Luca Ferrari
2022-09-29 2:28 ` Ihor Radchenko
2022-09-29 14:10 ` Luca Ferrari
2022-09-29 14:19 ` Ihor Radchenko
2022-10-05 6:03 ` Luca Ferrari
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h70tgddk.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fluca1978@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/org-mode.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).