From: Eli Zaretskii <eliz@gnu.org>
To: Geoff Shannon <geoffpshannon@gmail.com>
Cc: 17713@debbugs.gnu.org
Subject: bug#17713: First portion of `bt full`
Date: Fri, 06 Jun 2014 11:21:31 +0300 [thread overview]
Message-ID: <83egz24fec.fsf@gnu.org> (raw)
In-Reply-To: <CA+pAvvxkukXw1qHyEOihpSbLX8wppbYEmi4mm62Kqv+uHbgJmw@mail.gmail.com>
> From: Geoff Shannon <geoffpshannon@gmail.com>
> Date: Fri, 6 Jun 2014 01:06:43 -0700
> Cc: 17713@debbugs.gnu.org
>
> > Did you customize any GC-related options, like gc-cons-threshold?
>
> I didn't personally, but I use emacs Prelude which does this:
>
> (setq gc-cons-threshold 50000000)
That's 50MB! The default is 400000 (400K).
> I'm guessing that's likely the cause of this?
Could well be. It means Emacs invokes GC after it has created at
least 50MB worth of Lisp objects. Wading through all of them and
finding those which can be discarded will indeed take a while.
I suggest you remove that customization. The default is well tuned,
and you will hardly ever notice GC going on.
next prev parent reply other threads:[~2014-06-06 8:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 7:08 bug#17713: 24.3.91; Emacs hung in GC? Geoff Shannon
2014-06-06 7:13 ` bug#17713: First Portion of 'backtrace` Geoff Shannon
2014-06-06 7:14 ` bug#17713: First portion of `bt full` Geoff Shannon
2014-06-06 7:49 ` Eli Zaretskii
2014-06-06 7:57 ` Geoff Shannon
2014-06-06 8:00 ` Eli Zaretskii
2014-06-06 8:06 ` Geoff Shannon
2014-06-06 8:21 ` Eli Zaretskii [this message]
2014-06-06 8:51 ` Geoff Shannon
2014-06-06 13:46 ` Stefan Monnier
2014-06-06 7:32 ` bug#17713: Compressed Forms of 'backtrace' and 'bt full' output Geoff Shannon
2014-06-06 7:56 ` Eli Zaretskii
2014-06-06 7:59 ` Geoff Shannon
2014-06-06 8:04 ` Eli Zaretskii
2014-06-06 13:41 ` Stefan Monnier
2014-06-06 15:34 ` bug#17713: 24.3.91; Emacs hung in GC? Stefan Monnier
2014-06-08 22:01 ` Geoff Shannon
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=83egz24fec.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17713@debbugs.gnu.org \
--cc=geoffpshannon@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).