Date: Mon, 11 Oct 1999 23:04:44 -0700
From: Jay Cox [EMAIL PROTECTED]
Marc Lehmann wrote:
A normal user has nothing to do with the swap file, except that he will
find that his disk is full and many hours later he might even find the
reason
It will be much more
The following is not a real solution, but it I think it would make the user
understand the necessary internals better:
Add a second dialog to the "User Installation" process that explains the user
Gimp's way of handling memory and allows him to choose the size of the
tile-cache-size and the
]
To: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Date: 12 October 1999 05:34
Subject: Re: swap files
The following is not a real solution, but it I think it would make the user
understand the necessary internals better:
Add a second dialog to the "User Installation" process that explain
k call to the signal handlers and there is still a problem
with swap files being left around, we could fairly easily (nearly) guarantee that
any previous swapfiles left around by gimp running on the same host under the
same user are deleted the next time gimp is run. (embed the user name, IP
for /tmp but it is too small).
However, any other solution (doing it in the signal handler) is extremely
annyoing (leaves too many swap files around).
Are you sure about that? I think that it is more likely that the Gimp
crashes and calls the signal handler than to have a power failure
(which has
I think this will just give you the LENGTH of the file? So, I don't
know if it matters, but ISTR that Gimp uses files with holes, and
therefore LENGTH != SIZE.
Oh, I didn't know this.
In any case, the program *does* know (or should) know the number of
tiles that it can have (tile cache
On Mon, 11 Oct 1999, Marc Lehmann wrote:
In any case, why not use tmpfile or a similar function to create it? that
function will do exactly what is required and will work on all systems (as
good as it can).
Under Linux at least, tmpfile() simply does an unlink() after opening the
file. :-)
understand: can't you fstat your file handlers to compute used
space ?
I think unlinking the swap files in the signal handler that is called when we
crash would solve this problem. The cases where this will not work should be
rare enough not to worry about.
Well, power failures or cleaning people
On Sat, 09 Oct 1999, Adrian Likins wrote:
If I recall correctly, this has been suggested a few times
and made it into released versions of gimp at least once, only to be removed
later for reasons I do not recall. Seems like some sort of portability issues
perhaps, but its been a long time.
David Monniaux wrote:
Hi all,
Many people around here complain that Gimp leaves enormous swap files when
crashing. It is especially a pain since they are in a "hidden"
subdirectory.
Would it be possible to have Gimp unlink() the files after opening them?
I explain: if w
10 matches
Mail list logo
