Hi,
On Wed, 2007-03-14 at 09:01 -0700, William Skaggs wrote:
It might help if I explain a little more about how GIMP handles
memory. GIMP does not rely on the operating system for swapping.
When you start GIMP, it creates a file, of fixed size which you
designate in the Preferences, to
Hi,
On Tue, 2007-03-13 at 22:18 -0600, D. Stimits wrote:
There could be a mix of a gimp bug, and definitely some portion of my
plug-in. Although I know for a fact that I had a memory leak that was my
fault, the reaction to the leak was unexpected. The system in question
has only a /boot
[...] The thing I did not
expect was that it had well over a gig of ram left unused, no swap used,
30 gig of unused drive, and it still thought the hard drive was full.
[...]
It might help if I explain a little more about how GIMP handles
memory. GIMP does not rely on the operating system
On 3/14/07, William Skaggs wrote:
What is happening to you is that the swap file is filling up,
because data is accumulating there that ought to be cleared
away.
btw, is it possible to provide some feedback to users that available
resources are getting pretty close to zero?
Alexandre
On Wednesday 14 March 2007 17:01, William Skaggs wrote:
It might help if I explain a little more about how GIMP handles
memory. GIMP does not rely on the operating system for swapping.
When you start GIMP, it creates a file, of fixed size which you
designate in the Preferences, to serve as a
Hi,
On Mon, 2007-03-12 at 06:51 -0800, William Skaggs wrote:
I think you have hit an actual bug, and that it doesn't have anything
to do with python, because I have encountered a similar thing in a
modified version of gimpressionist that I worked up, written purely
in C. I believe that there
...
I think you have hit an actual bug, and that it doesn't have anything
to do with python, because I have encountered a similar thing in a
modified version of gimpressionist that I worked up, written purely
in C. I believe that there is some sort of memory leak that causes
gimp in some
I am hereforth asking you to apologise, if possible, both in private
and on the list for this message. We are runing a project needing
I cannot sincerely do so, in this instance. I do not apologize for
expressing my amusement, unless I judge that the situation was genuinely
worsened by my
On Mon, 12 Mar 2007 00:54:56 +0100, D. Stimits [EMAIL PROTECTED] wrote:
Speculating about why it claimed it was out of memory, I'm wondering if
the hard drive simply was too slow responding. It's a laptop, running
with core duo, entirely in ram. The drive is thus much slower than the
ability
Von: David Gowers [EMAIL PROTECTED]
I am hereforth asking you to apologise, if possible, both in private
and on the list for this message. We are runing a project needing
I cannot sincerely do so, in this instance. I do not apologize for
expressing my amusement, unless I judge that the
I think you have hit an actual bug, and that it doesn't have anything
to do with python, because I have encountered a similar thing in a
modified version of gimpressionist that I worked up, written purely
in C. I believe that there is some sort of memory leak that causes
gimp in some situations
On 3/12/07, D. Stimits [EMAIL PROTECTED] wrote:
I have not found any python-fu way to close a file, or to reclaim
memory after creating an image or layer. Is there such a thing? Is there
instead some sort of garbage collection?
hahahaha!
gimp.delete(image)
or
gimp.delete(layer) #only do
On Sunday 11 March 2007 20:54, D. Stimits wrote:
I have not found any python-fu way to close a file, or to reclaim
memory after creating an image or layer. Is there such a thing? Is
there instead some sort of garbage collection?
Speculating about why it claimed it was out of memory, I'm
13 matches
Mail list logo
