On Thu, Dec 13, 2001 at 08:28:37PM -0500, Jens Gecius wrote:
| Hi folks!
|
| I just started scanning a couple of negatives at 1600dpi and am trying
| to work with them in the gimp.
|
| Unfortunately, I don't see the gimp being nice to memory. I have 1G on
| board, a 768M swap partition, and /tmp has another 950M free. Alls
| available (swap actually was never used).
|
| Now I load ONE image (the scan, approx. 60M) in Gimp and usage of
| memory by gimp is 40M. *Additionally* Gimp eats up 430M (!!) in /tmp.
|
| And if I do some copy/paste-new/save/close, after 2 or 3 turns my /tmp
| is eaten up. No more space available. 950M eaten to keep ONE image??
| This seems to me kind of ridiciulous.
|
| Any idea how to cope that? I use image tile size 24M, conservative
| memory usage (tried without that - same).
|
| And please no hints like "get a bigger hd for tmp". This whole
| swapping while mem _is_ available makes no sense to me.
gimp does that because it is such a memory hog, and it wants to be
nicer to other apps. How many levels of undo have you enabled? 60MB
is a big picture, and if you do some operations, gimp must save the
old state of the image so that you can undo the operation. Thus lots
of memory/swap usage. If you reduce the size of the image, or the
resolution, it would decrease the resources required to process it.
HTH,
-D
--
He who finds a wife finds what is good
and receives favor from the Lord.
Proverbs 18:22
