Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-03-11 Thread Kevin Cozens
On 12-03-11 08:12 PM, Tom Vrankar wrote: only problems that remained were with the API. I guess there's a lot of history there, but inconsistencies in it make it a chore to learn. And when you call a function potentially thousands of times, you can't tolerate the pointlessly repeating "deprecated

Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-03-11 Thread Partha Bagchi
On Sun, Mar 11, 2012 at 8:12 PM, Tom Vrankar wrote: ...[deleted] > > The > only problems that remained were with the API. I guess there's a lot of > history there, but inconsistencies in it make it a chore to learn. And when > you call a function potentially thousands of times, you can't tolerate

Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-03-11 Thread Tom Vrankar
And now, the rest of the story. I've completed this project, and everything worked out. Turns out that my perceived "memory leak" was nothing more than normal growth of the undo stack; disable undos, and the problem goes completely away. As for gimp_image_delete(), it occurs as part of deleting

Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-02-28 Thread Michael Natterer
On Tue, 2012-02-28 at 10:52 -0500, Kevin Cozens wrote: > On 12-02-15 11:42 PM, Tom Vrankar wrote: > > Here's the simple command sequence that demonstrates the "leak". > [snip] > > img =gp.gimp_image_new (1280, 720, 0) > > dsp =gp.gimp_display_new (img) > > lyr =gp.gimp_layer_new_from_drawable (src.

Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-02-28 Thread Kevin Cozens
On 12-02-15 11:42 PM, Tom Vrankar wrote: Here's the simple command sequence that demonstrates the "leak". [snip] img =gp.gimp_image_new (1280, 720, 0) dsp =gp.gimp_display_new (img) lyr =gp.gimp_layer_new_from_drawable (src.layers[1], img) img.insert_layer (lyr, position =0) gp.gimp_display_del

[Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-02-20 Thread Crazy Aunt Gail's, LLC
On 02/16/2012 05:42 AM, Tom Vrankar wrote: >img =gp.gimp_image_new (1280, 720, 0) >dsp =gp.gimp_display_new (img) >lyr =gp.gimp_layer_new_from_drawable (src.layers[1], img) >img.insert_layer (lyr, position =0) >gp.gimp_display_delete (dsp) If you eschew creating a new display

Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-02-16 Thread Ofnuts
You should use gimp_image_delete() when you are done with one image. On 02/16/2012 05:42 AM, Tom Vrankar wrote: img =gp.gimp_image_new (1280, 720, 0) dsp =gp.gimp_display_new (img) lyr =gp.gimp_layer_new_from_drawable (src.layers[1], img) img.insert_layer (lyr, position =0) gp.gimp_display_del

Re: [Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-02-15 Thread David Gowers (kampu)
Hi Tom, On Thu, Feb 16, 2012 at 3:12 PM, Tom Vrankar wrote: > img =gp.gimp_image_new (1280, 720, 0) > dsp =gp.gimp_display_new (img) > lyr =gp.gimp_layer_new_from_drawable (src.layers[1], img) > img.insert_layer (lyr, position =0) > gp.gimp_display_delete (dsp) ..You are creating one image after

[Gimp-developer] Python FU Scripting -- Memory Leak? or How to release python gimp objects properly to manage memory usage?

2012-02-15 Thread Tom Vrankar
I'm using python-fu to script a sequence of animation frames in Partha's Gimp 2.7.5 for win 32 (Vista) (Thanks!) It's expected to be a relatively long sequence when done, probably several thousand frames, but the animation is pretty simple, very algorithmic, just a series of layer pans, zooms,