From: Miles Bader <miles@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Jashy <nanjunjie@gmail.com>, Emacs-devel@gnu.org
Subject: Re: Using the ImageMagick backend seems to leak memory
Date: Fri, 07 Jan 2011 16:25:24 +0900 [thread overview]
Message-ID: <buoei8pw4yj.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <87pqs99qjd.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Fri, 07 Jan 2011 15:27:50 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> > My impression is that in general, ImageMagick does not aim at memory
> > efficiency (that's why I don't want to use its libraries for my own
> > image I/O needs, event though doing so would be pretty convenient).
> > I would have though it's OK for small/medium images though.
>
> I believe disagreement on this point was a (minor) reason why the
> GraphicsMagick project forked off. Anyway, GraphicsMagick *does* aim
> at efficiency, both in time and space.
Sadly GraphicsMagick seems to have achieved this partly by dropping some
important features (e.g. floating-point pixel support...).
Probabably not relevant for Emacs I suppose.
What _I_ want, though, is a way to use one of these toolkits lower-level
way that allows me to do progressive/partial I/O. Unfortunately it
seems that most unified image-handling toolkits sort of ignore anything
but whole-image I/O...
-Miles
--
Generous, adj. Originally this word meant noble by birth and was rightly
applied to a great multitude of persons. It now means noble by nature and is
taking a bit of a rest.
next prev parent reply other threads:[~2011-01-07 7:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 7:51 Using the ImageMagick backend seems to leak memory Tassilo Horn
2011-01-06 9:02 ` joakim
2011-01-06 10:20 ` Tassilo Horn
2011-01-07 4:17 ` Jashy
2011-01-07 4:59 ` Miles Bader
2011-01-07 6:27 ` Stephen J. Turnbull
2011-01-07 7:25 ` Miles Bader [this message]
2011-01-07 8:28 ` Tassilo Horn
2011-01-07 22:39 ` Andreas Schwab
2011-01-10 10:34 ` Tassilo Horn
2011-01-10 13:28 ` Jashy
2011-01-10 13:56 ` Tassilo Horn
2011-01-10 14:36 ` Jashy
2011-01-11 10:14 ` Jashy
2011-01-11 10:59 ` joakim
2011-01-11 14:17 ` joakim
2011-01-11 14:38 ` joakim
2011-01-11 17:43 ` Tassilo Horn
2011-01-11 18:11 ` joakim
2011-01-11 19:10 ` Tassilo Horn
2011-01-11 19:35 ` joakim
2011-01-11 19:55 ` Tassilo Horn
2011-01-12 1:47 ` Stefan Monnier
2011-01-12 7:37 ` Tassilo Horn
2011-01-10 21:47 ` Tassilo Horn
2011-01-11 8:47 ` Tassilo Horn
2011-01-11 9:35 ` joakim
2011-01-11 9:53 ` Tassilo Horn
2011-01-11 9:54 ` joakim
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=buoei8pw4yj.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=nanjunjie@gmail.com \
--cc=stephen@xemacs.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).