top isn't actually a very accurate way of profiling memory usage. The
numbers you have shown so far can easily be explained by memory
fragmentation and the fact that glibc allocates memory in pools.
Smaller memory fragments are not returned to the operating system but
are being kept for reuse
Hi,
Jared Whiting [EMAIL PROTECTED] writes:
Is there any more information I can provide regarding my test script and
the memory increase I observe with GIMP? Following your advice I ran my
script more often, but I'm not sure if my response was what you were
looking for. If I run a script
top isn't actually a very accurate way of profiling memory usage. The
numbers you have shown so far can easily be explained by memory
fragmentation and the fact that glibc allocates memory in pools.
Smaller memory fragments are not returned to the operating system but
are being kept for reuse
Hi,
michael chang [EMAIL PROTECTED] writes:
What about putting $img = undef; at the end -- does this change anything?
Shouldn't really matter since gimp-perl runs in a separate process and
the original claim was that gimp was leaking memory, not gimp-perl.
Sven
How much memory increase do you see per image? Can you run this script
a couple of times and show us memory usage before and after?
Sven
When I first start up GIMP:
/usr/bin/gimp -d -i -c --batch '(extension-perl-server 1 0 0 )'
I see the following using top (script-fu and Perl-Server
On 8/17/05, Jared Whiting [EMAIL PROTECTED] wrote:
increase, but the cgi I'm using in production does a lot more than this
and can be generating a few thousand images in one day.
Are any of these concurrently, and if so how many; could this make a difference?
--
~Mike
- Just my two cents
-
Are any of these concurrently, and if so how many; could this
make a difference?
~Mike
In production there can definitely be concurrent image generation, which
might be playing a role in the issue I'm having there with increased
memory. With the test code though I'm just running the script
On 8/15/05, Jared Whiting [EMAIL PROTECTED] wrote:
machine because in the process of creating images the GIMP keeps holding
on to more and more memory. As an example, I can run the following
$img-gimp_image_undo_enable;
gimp_image_delete($img);
Gimp::end;
the GIMP instance grabs on to
Hi,
Jared Whiting [EMAIL PROTECTED] writes:
I am currently using GIMP 2.8 for GNU/Linux,
There is no such GIMP version (yet). What version are you really using?
Sven
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
... meant to write GIMP 2.2.8
-Original Message-
From: Sven Neumann [mailto:[EMAIL PROTECTED] On Behalf Of Sven Neumann
Sent: Tuesday, August 16, 2005 2:09 PM
To: Jared Whiting
Cc: gimp-developer@lists.xcf.berkeley.edu
Subject: Re: [Gimp-developer] Gimp_image_delete and adding
Hi,
Jared Whiting [EMAIL PROTECTED] writes:
... meant to write GIMP 2.2.8
Ok, your script actually looks as if it does the right thing, at least
on first sight. However, since we have run gimp-2.2 in a memory
profiler which didn't show any memory leaks, I am not yet convinced
that there's a
11 matches
Mail list logo
