From: Eli Zaretskii <eliz@gnu.org>
To: "ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>
Cc: chiaki.ishikawa@ubin.jp, larsi@gnus.org, 39413@debbugs.gnu.org,
npostavs@gmail.com
Subject: bug#39413: 26.2; Emacs gets hung
Date: Thu, 12 Aug 2021 10:10:25 +0300 [thread overview]
Message-ID: <838s17dtpa.fsf@gnu.org> (raw)
In-Reply-To: <277eef17-0241-7245-a801-dc3707c23e5b@yk.rim.or.jp> (ishikawa@yk.rim.or.jp)
> Cc: larsi@gnus.org, npostavs@gmail.com, 39413@debbugs.gnu.org,
> chiaki.ishikawa@ubin.jp
> From: "ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>
> Date: Wed, 11 Aug 2021 22:41:56 +0900
>
> What about the dump below, which was in the *Messages* buffer following
> dump I sent.
> I am afraid I picked up the wrong dump in my previous e-mail.
>
> Now, is "gc-elapsed" the elapsed time spent in the GC routine?
> If so, the two samples at the end of the dump here certainly look
> suspicious.
Yes, they show a couple of GCs that took about 150 to 200 sec. That
is indeed excessive, but gc-elapsed reports the wall-clock time, not
the CPU time, so if Emacs wasn't getting processing resources to run,
which could happen on a stressed system, that could explain the long
GC times. Note that other GC cycles, both before and after the 2
problematic ones, took much less time. And the statistics returned by
memory-use-counts doesn't show any excessive number of Lisp objects;
in fact, my current Emacs session, which runs for 9.5 days, has an
order of magnitude more objects than what you show, and yet GC cycles
here are barely perceptible.
next prev parent reply other threads:[~2021-08-12 7:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 9:32 bug#39413: 26.2; Emacs gets hung chiaki-ishikawa-thunderbird-account
2020-02-04 15:33 ` Eli Zaretskii
2020-02-05 1:11 ` chiaki-ishikawa-thunderbird-account
2020-02-21 17:27 ` Noam Postavsky
2020-02-22 17:53 ` chiaki-ishikawa-thunderbird-account
2020-04-28 21:36 ` ISHIKAWA,chiaki
2020-04-29 6:55 ` Eli Zaretskii
2020-04-30 2:45 ` chiaki-ishikawa-thunderbird-account
2020-05-20 4:31 ` chiaki-ishikawa-thunderbird-account
2020-05-25 12:15 ` Noam Postavsky
2020-05-25 15:50 ` chiaki-ishikawa-thunderbird-account
2020-06-08 8:17 ` chiaki-ishikawa-thunderbird-account
2021-08-10 16:09 ` Lars Ingebrigtsen
2021-08-11 1:08 ` ISHIKAWA,chiaki
2021-08-11 6:07 ` ISHIKAWA,chiaki
2021-08-11 7:22 ` ISHIKAWA,chiaki
2021-08-11 11:14 ` Lars Ingebrigtsen
2021-08-11 13:46 ` ISHIKAWA,chiaki
2021-08-11 11:47 ` Eli Zaretskii
2021-08-11 13:41 ` ISHIKAWA,chiaki
2021-08-12 7:10 ` Eli Zaretskii [this message]
2021-08-15 23:27 ` ISHIKAWA,chiaki
2021-08-16 0:20 ` ISHIKAWA,chiaki
2021-08-16 11:35 ` Eli Zaretskii
2021-08-20 1:56 ` ISHIKAWA,chiaki
2021-09-17 14:49 ` Lars Ingebrigtsen
2021-10-18 9:00 ` Lars Ingebrigtsen
2021-10-19 7:04 ` ISHIKAWA,chiaki
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=838s17dtpa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39413@debbugs.gnu.org \
--cc=chiaki.ishikawa@ubin.jp \
--cc=ishikawa@yk.rim.or.jp \
--cc=larsi@gnus.org \
--cc=npostavs@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.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).