Re: Gimp-Perl and Server Question
On Mon, Nov 15, 1999 at 03:29:39PM -0700, Greg Walters [EMAIL PROTECTED] wrote: How do you delete the image? I *know* that $image-delete sufficed to delete an image totally, but this was some months ago. That is what I essentially did using the gimp_image_new() and gimp_image_delete() subroutines. (ps: gimp-1.0 has various but rather small memory leaks so after millions of operations your perl-server and the gimp will grow by a few megabytes. This does not affect image deletion, however). This must be what I am seeing (as we are running gimp-1.0.4). I don't think so, as you would not see superflous layers! you must be hitting something larger. It *might* be possible that you would have to delete all layers first in 1.0 (but I can't really remember ;) in a cron (weekly or so) to kill Gimp and the Perl server and then restart them just to keep things under control. ... which is a sensible thing to do anyway. gimp was not really tested under this kind of conditions (not being a mere library). And, while I plugged all the memleaks I found in 1.0, 1.2 might just introduce new ones ;) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: Gimp-Perl and Server Question
After a little testing, using my button creator, I did notice that The Gimp's memory usage did increase after each execution. I found during testing that if I temporarily displayed the new image and then deleted it that the Layers Channels Image list did not retain the image created. However, this did not stop the memory grabbing. I can't answer your main question, but I'd like to comment on the fact the LC dialogs image preview shows all images regardless if they have a display or not. This can be quite useful for debugging sometimes, but I think this behaviour should be changed. Do you agree?? Salut, Sven
Re: Gimp-Perl and Server Question
After a little testing, using my button creator, I did notice that The Gimp's memory usage did increase after each execution. I found during testing that if I temporarily displayed the new image and then deleted it that the Layers Channels Image list did not retain the image created. However, this did not stop the memory grabbing. I can't answer your main question, but I'd like to comment on the fact the LC dialogs image preview shows all images regardless if they have a display or not. This can be quite useful for debugging sometimes, but I think this behaviour should be changed. Do you agree?? Default behaviour, OK, always no. I want to know why Gimp eat RAM when testing scripts, and which name I should use to recover that RAM. Go to Script-Fu console and delete by hand the offenders. GSR
Re: Gimp-Perl and Server Question
On Mon, Nov 15, 1999 at 09:20:22AM -0700, Greg Walters [EMAIL PROTECTED] wrote: During the testing of my programs I noticed that the Layers Channels palette had every image created still listed in the Image: pull-down list. This got me to thinking, is this information being kept around even though the image is long gone? If so, does that mean the Gimp-Perl server's memory usage would grow in size? testing that if I temporarily displayed the new image and then deleted it that the Layers Channels Image list did not retain the image How do you delete the image? I *know* that $image-delete sufficed to delete an image totally, but this was some months ago. It is possible that some new bug was introduced, though. (ps: gimp-1.0 has various but rather small memory leaks so after millions of operations your perl-server and the gimp will grow by a few megabytes. This does not affect image deletion, however). -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: Gimp-Perl and Server Question
Sven Neumann wrote: After a little testing, using my button creator, I did notice that The Gimp's memory usage did increase after each execution. I found during testing that if I temporarily displayed the new image and then deleted it that the Layers Channels Image list did not retain the image created. However, this did not stop the memory grabbing. I can't answer your main question, but I'd like to comment on the fact the LC dialogs image preview shows all images regardless if they have a display or not. This can be quite useful for debugging sometimes, but I think this behaviour should be changed. Do you agree?? Yes, it was useful for debugging. I was able to see what the end result was and where I might have problems (layer creation and merging, etc.). Marc Lehmann wrote: How do you delete the image? I *know* that $image-delete sufficed to delete an image totally, but this was some months ago. That is what I essentially did using the gimp_image_new() and gimp_image_delete() subroutines. (ps: gimp-1.0 has various but rather small memory leaks so after millions of operations your perl-server and the gimp will grow by a few megabytes. This does not affect image deletion, however). This must be what I am seeing (as we are running gimp-1.0.4). We may put in a cron (weekly or so) to kill Gimp and the Perl server and then restart them just to keep things under control. Thanks for all your help. Greg Walters Webmaster Harrison School District
