From: Len Trigg <lenbok@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 122@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
rms@gnu.org, handa@m17n.org
Subject: bug#122: 23.0.60; Slowdown in directory scanning over time.
Date: Mon, 15 Sep 2008 09:24:22 +1200 [thread overview]
Message-ID: <hbljxua0ah.wl%len@netvalue.net.nz> (raw)
In-Reply-To: <hbk5diovxd.wl%len@netvalue.net.nz>
Len Trigg wrote:
> (tramp-flush-file-function erc-kill-buffer-function browse-url-delete-temp-file jde-db-nullify-breakpoint-markers vc-kill-buffer-hook)
>
> I can try restarting my emacs without using some of those features for
> the next few days.
I think I have some more information on where those extra
code-conversion-work buffers are coming from. I have a crontab
scheduled script that regularly downloads ics calendar files from
various locations and uses icalendar.el to convert them to diary
format (which are then #included by my main diary file). This
conversion uses a separate "emacs -batch" process in order to not
interfere with my main emacs, and then finally calls emacsclient at
the end to tell my main emacs to update it's current diary display, if
present.
If I disable this script entirely, the code-conversion-work buffers
don't accumulate.
If I disable the final call to emacsclient, the code-conversion-work
buffers do still accumulate (eliminating emacsclient as the culprit).
If I disable global-auto-revert mode in my main emacs, the
code-conversion-work buffers don't accumulate.
So it seems to be related to the modified diary files being
auto-reverted. I have not managed to work out any more details than
that.
Regardless of why they are leaking, it seems to me that Richards
suggestion of eliminating the use of multiple code-conversion buffers
at all is probably the way to go.
Cheers,
Len.
next prev parent reply other threads:[~2008-09-14 21:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 22:29 bug#122: 23.0.60; Slowdown in directory scanning over time Chong Yidong
2008-08-27 3:02 ` Len Trigg
2008-08-31 21:57 ` Len Trigg
2008-09-02 1:09 ` Richard M. Stallman
2008-09-11 3:29 ` Len Trigg
2008-09-11 4:18 ` Chong Yidong
[not found] ` <E1KdpeJ-0004Sb-Oj@fencepost.gnu.org>
2008-09-11 22:35 ` Len Trigg
2008-09-12 0:42 ` Chong Yidong
2008-09-12 4:00 ` Len Trigg
2008-09-14 21:24 ` Len Trigg [this message]
2008-09-15 1:04 ` Kenichi Handa
2008-09-15 2:42 ` Len Trigg
2008-09-15 18:26 ` Richard M. Stallman
2008-09-16 1:09 ` Kenichi Handa
2008-09-16 16:18 ` Richard M. Stallman
2008-09-15 18:26 ` Richard M. Stallman
2008-09-16 1:27 ` Kenichi Handa
2008-09-16 13:25 ` Stefan Monnier
2008-09-17 2:19 ` Kenichi Handa
2008-09-17 16:02 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=hbljxua0ah.wl%len@netvalue.net.nz \
--to=lenbok@gmail.com \
--cc=122@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=handa@m17n.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.