unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Layer <layer@franz.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: huge files in ~/.emacs.d/auto-save-list/
Date: Mon, 21 May 2007 23:55:25 +0300	[thread overview]
Message-ID: <uejl9lww2.fsf@gnu.org> (raw)
In-Reply-To: <17763.1179779953@gemini.franz.com> (message from Kevin Layer on Mon, 21 May 2007 13:39:13 -0700)

> Date: Mon, 21 May 2007 13:39:13 -0700
> From: Kevin Layer <layer@franz.com>
> 
> I just deleted 2.7 GB (yes, you read that right) of files in the above
> named directory.  Wow.  
> 
> The size and contents of 98% of the files in that directory look OK
> (all less than 2K and are a series of pathnames, one per line).  Some
> of the files, however, are really enormous.  They all start out OK,
> but have complete garbage in them after a certain point.  Sometimes
> mail messages.  Sometimes binary data.
> 
> I've seen this on several machines around here, and under several
> users accounts, so it is not isolated to my .emacs/uid.
> 
> Anyone else seen this?  I found only one reference in google
> (http://ww.telent.net/diary/2004/7/#4.78600) to the problem.  It's
> rather hard to search using ".saves-", unfortunately.
> 
> I can easily write a cron job to clean up the problem, but it feels
> like a pretty bad bug to me.

Thanks for reporting, but please provide the necessary details: the
OS, the Emacs version, the works (M-x report-emacs-bug RET will do
that for you).

FWIW, the largest file in my .emacs.d/auto-save-list/ directory is
13KB big, and it has no garbage in it.  There are 75 files there,
created during a year-long period.  This is (various pretests of)
Emacs 22.1 on MS-Windows XP SP2.

In general, if the garbled files were produced by a session that
crashed, that could explain the garbage: after all, Emacs is in deep
trouble when it crashes, and your description sounds like Emacs had
its memory badly trashed.  But I agree that it's a nasty problem that
should be tracked down.  The problem is, we cannot easily do that
without some kind of recipe for reproducing the problem.

  reply	other threads:[~2007-05-21 20:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 20:39 huge files in ~/.emacs.d/auto-save-list/ Kevin Layer
2007-05-21 20:55 ` Eli Zaretskii [this message]
2007-05-21 21:47   ` Kevin Layer
2007-05-22 14:52 ` Richard Stallman
2007-05-22 15:06   ` Kevin Layer
2007-05-22 23:10     ` Richard Stallman
2007-05-22 23:26       ` Kevin Layer
2007-05-23 18:56         ` Richard Stallman
2007-05-23 19:33           ` Kevin Layer
2007-05-24 10:55             ` Richard Stallman
2007-05-24 14:43               ` Kevin Layer
2007-05-26  0:19                 ` Richard Stallman
2007-05-23 19:42           ` Kevin Layer
2007-05-23  9:32       ` Andreas Schwab
2007-05-23 11:47         ` Eli Zaretskii
2007-05-23 23:45           ` Richard Stallman
2007-05-23 18:56         ` 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=uejl9lww2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=layer@franz.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).