From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [emacs_user@hotmail.com: reproducible cygwin memory problems]
Date: Fri, 04 Aug 2006 08:48:01 +0200 [thread overview]
Message-ID: <85fygdkndq.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1G8odT-0002JR-Ke@fencepost.gnu.org> (Richard Stallman's message of "Thu, 03 Aug 2006 21:37:59 -0400")
Richard Stallman <rms@gnu.org> writes:
> Would someone please help him investigate this -- then ack this message?
>
> Are the images kept in a cache? Is there a way to clear it?
>
They are, and he does already clear the cache:
> after killing the buffer with the image and using
> M-:(clear-image-cache t)RET: 16476;
Incidentally, the cache is there since we are very inefficient turning
image data into images: it would probably make sense to let gdk (or
equivalent code working on entire images) handle this where available
(the main problem is that the conversion is done pixel-by-pixel).
But that is a long-standing peeve of mine, and certainly not something
to be tackled for Emacs 22.
The memory issues, however, are a different thing. I guess it might
be because image data gets allocated by xmalloc, out of Emacs' memory
pool. xmalloc would not be able to make use of previous small memory
allocations.
> after editing a large image: 39164;
>
> again quit+clear cache: 34484;
>
> edit small+medium+large images: 58936;
>
> quit+clear: 87636... (increased!)
>
> I hope someone can look into this, and I am happy to provide
> information given specific instructions.
>
> thanks... EU
>
>
> In GNU Emacs 22.0.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
> of 2006-07-31 on cata2
The problem might be related to the "malloc" or equivalent memory
allocation strategy that is available on a copmilation for Cygwin.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2006-08-04 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 1:37 [emacs_user@hotmail.com: reproducible cygwin memory problems] Richard Stallman
2006-08-04 6:48 ` David Kastrup [this message]
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=85fygdkndq.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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.