Re: [Gimp-developer] memory manage in python-fu
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 behaviour. It's certainly true that my message can be misinterpreted -- on the net, it's probably wisest to just assume no hidden meanings -- if it looks like a fish, assume it is a fish (and nothing more). much of new developers and contributors, and are in no position of theating anyone like this. Please perceive I am no "police" - I am asking this personally, but I also have promised the people organizing the LGM I'd tlak to gimp developers to try to make the enviroment more frindly to newcomers. In my observation, friendly sometimes is not polite -- for instance, answering as I did rather than giving a detached commentary free of any emotional context at all. This is why I view the way I replied as better (and certainly more friendly) than most previous mails of mine on this list. (btw, having to explicitely delete a python object __is__ a bug - objects that are seeing in python should be garbage collected when they are no longer referecenced. ) I avoided commenting on that because it wasn't clear whether they actually were no longer referenced. I certainly agree that there is something wrong with the gimp.delete convention here -- it only behaves how I'd expect sometimes. I'd definitely like to see more PyGimp developers myself -- hardly anyone seems to make as extensive use of it as I do. Perhaps a standard module path for pygimp plugins could be worked out (arguably, the PDB removes this need, but the PDB is cranky to use compared to Python modules) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] memory manage in python-fu
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 to consume ram. How does gimp determine that there is no space > left on the device...is it a timeout in addition to other means? I saw something a little like this recently. I cant document it thoroughly but here's a resumé in case it's related. I tried to open about eight multi-megabyte jpeg images in one open operation not wanting to go through the labourious open dialogue eight times and not noticing quite how big they were. I was half expecting some error after a few were opened but expected error trapping to handle it correctly. What I ended up with was a completely unstable mess which I had to clean up with xkill , restart the xserver and a bit of ps and kill to clean up the residue. Now this could be regarded as extreme conditions and represents a good stress test. It seems running out of RAM and/or swap is not properly error trapped. I just throw this info in in case it relates the this script issue posted. gg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] memory manage in python-fu
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 situation was genuinely > worsened by my behaviour. We could make it the policy that anyone who does shout "RTFM!" has to: - make sure that there is a FM - make sure that it is up-to-date - provide the URL In this case, this would be like: "RTFM! http://www.gimp.org/docs/python/index.html"; I'll leave the check whether this is up-to-date for David as an exercise :) HTH, Michael -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] have a look in our kitchen...
guys + gals, thanks to Sven, the GIMP UI redesign team has now a wiki where everybody can follow our progress: http://gui.gimp.org Right now we are filling it with our raw evaluation notes. Some of the latest added stuff is so raw that you can track us clarifying it a couple of days afterwards. The wiki is an exiting experiment (for me) in collaboration and communication. It functions as our documentation and for your insight and entertainment. It is not meant to start a flame war. Enjoy reading about our journey, --ps principal user interaction architect man + machine interface works http://mmiworks.net/blog : on interaction architecture ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] about gimp_zoom_preview_new
Pals, I realized that gimp 2.3.15 (and some versions before) comes with zoom for previews. A very useful feature for what I want to develop (a noise reduction plugin). I added a line 'gimp_zoom_preview_new (drawable);' that I got from http://developer.gimp.org/api/2.0/libgimp/GimpZoomPreview.html The plugin complies just fine, but when trying to run it in gimp 2.3.15 the plugin crashes with a message in the console: : symbol lookup error: : undefined symbol: gimp_zoom_preview_new (gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3: plug_in_flush(): error: Broken pipe So, what am I doing wrong? Thanks! Luis. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] memory manage in python-fu
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 to maintain reference to tiles that are no longer being used in any way, and it is something that shows up when you create and delete layers over and over again, in a certain way. So it would probably be useful for you to file a bug report about this, if you would. The memory that is being exhausted, by the way, is the "swap" area that gimp allocates on the hard disk each time you run it. The tile manager moves tile data there if space is needed. -- Bill __ __ __ __ Sent via the CNPRC Email system at primate.ucdavis.edu ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp_zoom_preview_new
On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit <[EMAIL PROTECTED]> wrote: > (gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3: > plug_in_flush(): error: Broken pipe This is nothing to do with the zoom preview mate, you've got a blocked toilet !! I should call out a plumber , this could get messy. This often happens in older properties due to subsidence or nearby tree roots. LOL ! sorry , had to laugh at the way that error came out. ;) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp_zoom_preview_new
Hi, On Mon, 2007-03-12 at 11:22 -0300, Luis A. Florit wrote: > I added a line 'gimp_zoom_preview_new (drawable);' that I got from > http://developer.gimp.org/api/2.0/libgimp/GimpZoomPreview.html > The plugin complies just fine, but when trying to run it in > gimp 2.3.15 the plugin crashes with a message in the console: > > : symbol lookup error: : > undefined symbol: gimp_zoom_preview_new Looks like the plug-in is not picking up recent enough versions of libgimpui. Try ldd on the executable. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
> On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit > <[EMAIL PROTECTED]> wrote: > > > (gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3: > > plug_in_flush(): error: Broken pipe > > This is nothing to do with the zoom preview mate, you've got a > blocked toilet!! I should call out a plumber, this could get messy. > This often happens in older properties due to subsidence or nearby > tree roots. > > LOL ! > > sorry, had to laugh at the way that error came out. ;) Sorry, I didn't understand your answer... I just want to add zoom buttons to the preview window. I saw that many plugins use this. How to do it? Thanks, Luis. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] changes in script-fu in 2.3.14
Hi, On Fri, 2007-02-02 at 03:56 -0800, Saul Goode wrote: > I have a rough draft of some of the differences between SIOD-fu. It is > not yet comprehensive but perhaps it might be useful as a starting point. > > http://flashingtwelve.brickfilms.com/GIMP/Scripts/Script-fu-2/Reference/SIODdifferences-0.1.txt I get an error "403 Forbidden" when trying to reach this address? Did you take the document down or is there just a permission problem? Is there a newer version I should try? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp_zoom_preview_new
I've been on this mailing list for two days and this is the second time I've seen someone arrogantly laughing at someone's very reasonable questions. Chris Seaton On 12 Mar 2007, at 17:16, [EMAIL PROTECTED] wrote: > On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit > <[EMAIL PROTECTED]> wrote: > >> (gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3: >> plug_in_flush(): error: Broken pipe > > This is nothing to do with the zoom preview mate, you've got a blocked > toilet !! I should call out a plumber , this could get messy. This > often > happens in older properties due to subsidence or nearby tree roots. > > LOL ! > > > sorry , had to laugh at the way that error came out. ;) > ___ > Gimp-developer mailing list > Gimp-developer@lists.XCF.Berkeley.EDU > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
> Hi, > > On Mon, 2007-03-12 at 11:22 -0300, Luis A. Florit wrote: > > > I added a line 'gimp_zoom_preview_new (drawable);' that I got from > > http://developer.gimp.org/api/2.0/libgimp/GimpZoomPreview.html > > The plugin complies just fine, but when trying to run it in > > gimp 2.3.15 the plugin crashes with a message in the console: > > > > : symbol lookup error: : > undefined symbol: gimp_zoom_preview_new > > Looks like the plug-in is not picking up recent enough versions of > libgimpui. Try ldd on the executable. Mmmm... I see... # ldd .gimp-2.3/plug-ins/anulardenoise linux-gate.so.1 => (0x00cf4000) libgimpui-2.0.so.0 => /usr/lib/libgimpui-2.0.so.0 (0x004f1000) libgimpwidgets-2.0.so.0 => /usr/lib/libgimpwidgets-2.0.so.0 (0x003db000) libgimp-2.0.so.0 => /usr/lib/libgimp-2.0.so.0 (0x0034d000) libgimpcolor-2.0.so.0 => /usr/lib/libgimpcolor-2.0.so.0 (0x002cc000) libgimpmath-2.0.so.0 => /usr/lib/libgimpmath-2.0.so.0 (0x00101000) libgimpbase-2.0.so.0 => /usr/lib/libgimpbase-2.0.so.0 (0x0033c000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x04fa) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x053b) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x02aaa000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x029d8000) libm.so.6 => /lib/libm.so.6 (0x00d4a000) libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x0543f000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x0533f000) libcairo.so.2 => /usr/lib/libcairo.so.2 (0x02a3c000) libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x02979000) libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x029d3000) libdl.so.2 => /lib/libdl.so.2 (0x00d73000) libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x028d9000) libc.so.6 => /lib/libc.so.6 (0x0011) libgimpmodule-2.0.so.0 => /usr/lib/libgimpmodule-2.0.so.0 (0x00297000) libX11.so.6 => /usr/lib/libX11.so.6 (0x00ae4000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x0278c000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x0274f000) libXext.so.6 => /usr/lib/libXext.so.6 (0x00d9b000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00de9000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00dfa000) libXi.so.6 => /usr/lib/libXi.so.6 (0x02a32000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00df4000) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x0278) /lib/ld-linux.so.2 (0x00bea000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x0538) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x026a5000) libz.so.1 => /usr/lib/libz.so.1 (0x00d79000) libpng12.so.0 => /usr/lib/libpng12.so.0 (0x02727000) libXau.so.6 => /usr/lib/libXau.so.6 (0x00d8e000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00d93000) libexpat.so.0 => /lib/libexpat.so.0 (0x00dc6000) I compiled gimp with './configure --prefix=/opt/gimp' for it not to touch my stable gimp 2.2 RPM install. I am compiling the plug-in with /opt/gimp/bin/gimptool-2.0 --install Thanks, Luis. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
Hi, On Mon, 2007-03-12 at 19:11 -0300, Luis A. Florit wrote: > I compiled gimp with './configure --prefix=/opt/gimp' > for it not to touch my stable gimp 2.2 RPM install. > I am compiling the plug-in with > > /opt/gimp/bin/gimptool-2.0 --install You will probably have to set PKG_CONFIG_PATH to get this right. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp_zoom_preview_new
Chris Seaton wrote: > I've been on this mailing list for two days and this is the second > time I've seen someone arrogantly laughing at someone's very > reasonable questions. Took me some time to get the joke, but it is one, IMO: > On 12 Mar 2007, at 17:16, [EMAIL PROTECTED] wrote: > >> On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit >> <[EMAIL PROTECTED]> wrote: >> >>> (gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3: The "punchline" is the following: >>> plug_in_flush(): error: Broken pipe >> This is nothing to do with the zoom preview mate, you've got a blocked >> toilet !! I should call out a plumber , this could get messy. flush() does get the toilet reference, broken pipe to the "blocked" (although it is debatable if "broken" and be read as "blocked" in this case) >> sorry , had to laugh at the way that error came out. ;) The last line should show how this message was meant to be understood - and it does hint towards the reason as well. HTH, Michael -- GIMP > http://www.gimp.org | IRC: irc://irc.gimp.org/gimp Wiki > http://wiki.gimp.org | .de: http://gimpforum.de Plug-ins > http://registry.gimp.org | ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
Hi, On Mon, 2007-03-12 at 23:13 +0100, Sven Neumann wrote: > You will probably have to set PKG_CONFIG_PATH to get this right. Thinking about it, perhaps gimptool-2.0 should do this for you. We could add something like PKG_CONFIG_PATH=$libdir/pkgconfig:$PKG_CONFIG_PATH to gimptool-2.0.in. Would this be a good idea or am I missing something? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
Hi Sven, > On Mon, 2007-03-12 at 19:11 -0300, Luis A. Florit wrote: > > > I compiled gimp with './configure --prefix=/opt/gimp' > > for it not to touch my stable gimp 2.2 RPM install. > > I am compiling the plug-in with > > > > /opt/gimp/bin/gimptool-2.0 --install > > You will probably have to set PKG_CONFIG_PATH to get this right. I am doing something wrong... I tried with this command: export PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig ; /opt/gimp/bin/gimp-2.3 and I still having the same error. Thanks, Luis. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
On Mon, 12 Mar 2007 19:36:42 -0300, "Luis A. Florit" <[EMAIL PROTECTED]> said: > I am doing something wrong... I tried with this command: Yes, yes you are. > export PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig ; /opt/gimp/bin/gimp-2.3 > > and I still having the same error. PKG_CONFIG_PATH only affects where stuff looks as it gets compiled. Also, you'd want to use PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig:$PKG_CONFIG_PATH, to keep the old stuff in there (assuming it's non-empty). IIRC, you'd want to set $LD_LIBRARY_PATH=/opt/gimp/lib/ for runtime. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
gg, I didn't get your joke at a first sight. English is not my language... BTW, it was funny. :) L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
Hi Ori, * El 12/03/07 a las 19:55, Ori Bernstein chamullaba: > On Mon, 12 Mar 2007 19:36:42 -0300, "Luis A. Florit" > <[EMAIL PROTECTED]> said: > > > I am doing something wrong... I tried with this command: > > Yes, yes you are. > > > export PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig ; /opt/gimp/bin/gimp-2.3 > > > > and I still having the same error. > > PKG_CONFIG_PATH only affects where stuff looks as it gets compiled. Also, > you'd > want to use PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig:$PKG_CONFIG_PATH, to keep > the old stuff in there (assuming it's non-empty). > > IIRC, you'd want to set $LD_LIBRARY_PATH=/opt/gimp/lib/ for runtime. Interesting. In fact, I didn't recompile GIMP, I only did a export LD_LIBRARY_PATH=/opt/gimp/lib:$LD_LIBRARY_PATH and the zoom preview worked! :) However, I am getting many errors. One of them is due to the fact that I don't know how to retrieve the origin of the preview. For non-zoom previews, the funcion 'gimp_preview_get_position' gives you the origin. I wasn't able to find the correspoding one for zoom_preview (gimp_zoom_preview_get_position does not exist?!). Another one is that I don't know which is the equivalent to 'gimp_drawable_preview_draw_region' for zoom_preview. Thanks for the help, and the prompt answers!!! Luis. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] memory manage in python-fu
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 is some sort of memory leak that causes > gimp in some situations to maintain reference to tiles that are no > longer being used in any way, and it is something that shows up when > you create and delete layers over and over again, in a certain way. > So it would probably be useful for you to file a bug report about this, > if you would. It would only be useful if that bug report included a way to reproduce the problem. And it would probably be helpful to discuss that code example beforehand. I am not saying that there are no memory leaks in GIMP. But we are frequently testing the software for this and I am not aware of any major memory leaks such as the one that Bill describes here. > The memory that is being exhausted, by the way, is the "swap" area > that gimp allocates on the hard disk each time you run it. The > tile manager moves tile data there if space is needed. Actually, it doesn't do that when space is needed, but when the memory allocated for tiles exceeds the limit configured as 'tile-cache-size'. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
Hi, On Mon, 2007-03-12 at 19:36 -0300, Luis A. Florit wrote: > I am doing something wrong... I tried with this command: > > export PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig ; /opt/gimp/bin/gimp-2.3 > > and I still having the same error. Are you actually using the LD_LIBRARY_PATH environment variables as explained in the release notes for the development version? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about gimp zoom preview new
Hi, On Mon, 2007-03-12 at 23:13 -0300, Luis A. Florit wrote: > However, I am getting many errors. One of them is due to the > fact that I don't know how to retrieve the origin of the preview. > For non-zoom previews, the funcion 'gimp_preview_get_position' > gives you the origin. I wasn't able to find the correspoding one > for zoom_preview (gimp_zoom_preview_get_position does not exist?!). GimpZoomPreview is derived from GimpPreview so you can use all methods from GimpPreview. > Another one is that I don't know which is the equivalent to > 'gimp_drawable_preview_draw_region' for zoom_preview. Perhaps have a look at one of the many plug-ins in the source distribution that use a GimpZoomPreview... Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
