unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: 17395@debbugs.gnu.org
Subject: bug#17395: GC during idle time becomes fatal
Date: Sat, 03 May 2014 04:00:38 -0400	[thread overview]
Message-ID: <E1WgUsA-0004J2-Au@fencepost.gnu.org> (raw)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I updated from the trunk on May 1, and since then, Emacs seems to GC a
lot when idle.  I am not sure it is GC, but I don't know what else it could be,
and a couple of times Emacs died because I typed C-g at it during that time
and said it was fatal to have an error in GC.

(It is a bug that C-g C-g during GC causes a crash.)

Over time, GC takes longer and longer.  Once I had to kill Emacs
because it went a few minutes without finishing a GC.  A couple of
times, it crashed saying memory was full.

The previously reported problem, applying to epa decryption still
occurs: decryption never finishes.  When I type C-g while it is hung,
I get a message asking me whether to kill the epa process that is
still running.  If I say yes, Emacs responds again but the decryption
has not been done.

I could get more info about that, with some trouble.

I don't know how to give more info about the GC problem.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.






             reply	other threads:[~2014-05-03  8:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-03  8:00 Richard Stallman [this message]
2014-05-03  8:23 ` bug#17395: GC during idle time becomes fatal Eli Zaretskii
2014-05-04  4:11   ` Richard Stallman
2014-05-04  4:00 ` Stefan Monnier
2014-05-05  6:59   ` Richard Stallman
2014-05-05  7:00   ` Richard Stallman

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=E1WgUsA-0004J2-Au@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=17395@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).