Gimp-Perl memory leak

[Andrei Simion]

Hi,

This is what you said:

<quote>
So you may have to free all tiles before the swap file
resizes itself to zero.
</quote>

How can I free the tiles in the swap? That was the question.

If I show you a 20 lines script, then you'd have to generate the image
maybe a million times to actually increase the swap. As Kevin said,
there may be a leak in one of the method calls inside the script. And
there are 104 calls.

Andrei

Sven Neumann wrote:

> Hi,
>
> On Sat, 2008-03-29 at 15:34 -0400, Andrei Simion wrote:
>
>> I read that the tiles in the files should be empty in order to allow the
>> swap to resize itself. But how I can do that? Is there a method that
>> should be called after deleting the image?
>
> Sorry, but you obviously do not understand what I am trying to explain.
> It probably doesn't make sense to continue this discussion further.
> Please show us a small script that allows us to reproduce the problem
> and we will check if there's a problem in the GIMP code that needs to be
> solved.
>
>
> Sven
>

_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[gg-6]

On Sat, 29 Mar 2008 23:26:34 +0100, Andrei Simion <ansi@...>  
wrote:

> If I show you a 20 lines script, then you'd have to generate the image
> maybe a million times to actually increase the swap. As Kevin said,
> there may be a leak in one of the method calls inside the script. And
> there are 104 calls.
> Andrei


I think that's the point. It's your task to find out which (if any) of  
those 140 calls is causing a leak. If you can demonstrate a clearly  
defined reproducible problem it will get dealt with.

If the short script needs to run in a loop that can be arranged or the  
script can repeat the action if that is what is causing the problem.

It's also possible that in simplifying the script you will find an error  
you have overlooked.

In my experience, there's no better way to find a bug in your own software  
than to draft a detailed bug report about it being due to the other  
software you are using.

As Sven said , there is little point in continuing to discuss this until  
you can provide something clear and reproducible.

"I have 630 lines with 140 calls that has a bug but I cant show you"  
clearly will not get dealt with.


/gg

--

   .*.
   /V\
  (/ \)
  (   )
  ^^_^^
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Kevin Cozens-2]

Seth Burgess wrote:
> Way cool on someone doing gimp-perl work again!  Sorry I've completely
> abandoned it, but I've got good reasons such as:

Congratulations on your latest "development project"! It is certainly of more
importance than gimp-perl. The only downside being it is a long term project
requiring approximately 18+ years of hands-on time. :-)

--
Cheers!

Kevin.

http://www.ve3syb.ca/           |"What are we going to do today, Borg?"
Owner of Elecraft K2 #2172      |"Same thing we always do, Pinkutus:
                                 |  Try to assimilate the world!"
#include <disclaimer/favourite> |              -Pinkutus & the Borg

_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer