Re: [Gimp-developer] The Occasional Bug List
David Neary wrote: Garry R. Osgood wrote: snip comment I'd suggest adding this comment to bugzilla, and closing the bug as NOTGIMP or NOTGNOME, or whatever bugzilla status corresponds to SEP (someone else's problem). Apologies - this comment (with lots more information) is already attached to the bug report. I just thought of something else - can we close this bug as a duplicate of the GTK+ bug? Cheers, Dave. -- David Neary, Marseille, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
Hi, David Neary [EMAIL PROTECTED] writes: After several months without one, the time has come to let ye know about the nice bugs that are still in the GIMP, and need fixing. Most of these are fairly shallow bugs against 1.2, some are meatier ones against 1.3. In any case, since the GIMP is now 3rd in the bugs open ranks on bugzilla.gnome.org (behind gtk+ and galeon) and have recently passed nautilus, we have some bug-fixing to do. I just found that I clicked the wrong link on bugzilla. The page I used to look at it still shows a not-so-bad picture: http://bugzilla.gnome.org/weekly-bug-summary.cgi However 280 open bugs (excluding enhancement requests) are still way too many. If you want to spend some time on this stuff, the bugs that have the target milestone set to 1.2.4 are especially important to look at: IDSev Pri State Summary 84884 nor Nor UNCO gimp-perl man pages claims wrongs statements 83362 blo Urg NEW Incompatible licenses used in the GIMP 69085 nor Hig NEW gdyntext loses state when editing pre-existing text 3340 min Nor NEW gDynText crops text 10466 nor Nor NEW I have some pb with rotation 21028 tri Nor NEW should warn user about enormous memory consumption 26072 nor Nor NEW initial_sub_region:: error :: src-w * (src-bytes 52543 nor Nor NEW bumpmap: bumpmapping off by 1 57952 min Nor NEW no scrollable scroll bars in new picture from a sel 71478 min Nor NEW Imagemap plug-in does not draw some rectangles corr 73891 nor Nor NEW bugs in the script-fus from the Alpha to Logo secti 79754 nor Nor NEW Text tool should use gdk_fontset_load() 82465 min Nor NEW CML explorer plugin incorrect for grayscale images 82671 nor Nor NEW Flattening while thresholding causes segfault 82763 nor Nor NEW xbm plugin emits malformed xbms 84145 nor Nor NEW Narrow straight lines are imprecise 86637 nor Nor NEW Small Tiles filter: apply filter + UNDO + Repeat La 87687 tri Nor NEW ImageMap should use lowercase, not uppercase tags 89274 nor Nor NEW Gradient Editor crashes when shift dragging a segme 89801 nor Nor NEW Gimp crashes when choosing a non-integer font size 92377 nor Nor NEW missing brush-dialog.png in help .. 94979 min Nor NEW Zoom is broken for very large images 83458 tri Low NEW Suggested improvement in a translated menu 58848 nor Hig ASSI Font problem 22360 nor Nor REOP nav panner race can leave the panner active but not 52866 min Nor REOP gimp-remote is not perfect 88278 maj Nor REOP Text tool fills text with strange semi-transparent Happy Bug-Hunting, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
On Thu, Nov 07, 2002 at 11:46:14AM +0100, Sven Neumann [EMAIL PROTECTED] wrote: However 280 open bugs (excluding enhancement requests) are still way Could somebody with sufficient priviledges allow me to edit bug reports again (account [EMAIL PROTECTED])? ;) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
On Wed, 6 Nov 2002, David Neary wrote: 78064 Entering large dimensions in Scale Image causes fatal error Memory issue - some things use lots of memory and crash the GIMP. Enhancement, marked critical - it's a matter of pre-calculating how big the new image will use, and warning the user if it goes over some threshold (say 1GB?) I think it's safe to say that if the size of the image is bigger than the size of the tile cache, it's big enough to warn about. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
Nathan Carl Summers wrote: On Wed, 6 Nov 2002, David Neary wrote: 78064 Entering large dimensions in Scale Image causes fatal error Memory issue - some things use lots of memory and crash the GIMP. Enhancement, marked critical - it's a matter of pre-calculating how big the new image will use, and warning the user if it goes over some threshold (say 1GB?) I think it's safe to say that if the size of the image is bigger than the size of the tile cache, it's big enough to warn about. Seems like a reasonable metric - but the default tile cache is 32M, and most people have upwards of 128M RAM these days. Maybe if we were to use this metric we should consider upping the default tile cache to at least 64M? If you're loading images from a camera with 3 megapixels, 32M is big enough to have 1 image open with 2 layers and no undo levels. Which seems a little harsh :) Cheers, Dave. -- David Neary, Marseille, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
On Wed, 2002-11-06 at 22:54, David Neary wrote: Seems like a reasonable metric - but the default tile cache is 32M, and most people have upwards of 128M RAM these days. Maybe if we were to use this metric we should consider upping the default tile cache to at least 64M? If you're loading images from a camera with 3 megapixels, 32M is big enough to have 1 image open with 2 layers and no undo levels. Which seems a little harsh :) In libgphoto2, someone recently implemented reading the available memory from /proc/meminfo (if available) and act according to that. The code is at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/gphoto/libgphoto2/libgphoto2/gphoto2-filesys.c?rev=HEADcontent-type=text/vnd.viewcvs-markup Look for gp_get_free_memory. Lutz -- +--+ | Lutz Müller +49 (7156) 34837 | | | | Hans-Sachs-Strasse 5 | | 71254 Ditzingen http://www.topfrose.de | | Germany [EMAIL PROTECTED] | +--+ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
On Wed, 2002-11-06 at 23:05, David Neary wrote: Looks kind of plaform-specific... how would you go about doing that for Solaris, SGI or Windows? Alternatively, if someone hacks up a plain-C-library called libmem or similar for figuring out free memory and stuff like that on various systems, we can join the efforts in gimp and libgphoto2. Lutz -- +--+ | Lutz Müller +49 (7156) 34837 | | | | Hans-Sachs-Strasse 5 | | 71254 Ditzingen http://www.topfrose.de | | Germany [EMAIL PROTECTED] | +--+ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
On 7 Nov 2002, Lutz Müller wrote: On Wed, 2002-11-06 at 23:05, David Neary wrote: Looks kind of plaform-specific... how would you go about doing that for Solaris, SGI or Windows? Alternatively, if someone hacks up a plain-C-library called libmem or similar for figuring out free memory and stuff like that on various systems, we can join the efforts in gimp and libgphoto2. It would be a nice thing to put in glib. Regardless, it should only be used to create a suggestion -- the tile cache size should still be determined by the user. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
Hi, Nathan Carl Summers [EMAIL PROTECTED] writes: On Wed, 6 Nov 2002, David Neary wrote: 78064 Entering large dimensions in Scale Image causes fatal error Memory issue - some things use lots of memory and crash the GIMP. Enhancement, marked critical - it's a matter of pre-calculating how big the new image will use, and warning the user if it goes over some threshold (say 1GB?) I think it's safe to say that if the size of the image is bigger than the size of the tile cache, it's big enough to warn about. remember that we already have a setting for more or less precisely that value in the prefs (max-new-image-size). I'd suggest we just use it then. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] The Occasional Bug List
David Neary wrote: Hi all, 10498 Marching Ants die untimely deaths This has been around for yonks - anyone want to look at it? I look at it from time to time -- I keep track of all my beasty bug children. This depends on GTK1.2 Bug #32617 being fixed (gdk_pointer_grab() Behaves Differently for X Input Events), and apparently that is not going to be done for the 1.2 series (See Owen Taylor's Additional Comment for this item) It has been moved to resolution in the GTK2.0 series, but Ipresume, being that it is still open, (moved to milestone 2.0.3) that a corresponding fix for Gimp 1.3 is also in a dependent state. A gimp-only fix for 1.2.3 against GTK1.2.x -- which won't see a GTK-based solution -- is conceivable:Not 'hard', but 'tedious.' It means, at the application level (in all the tool implementations that look for a release to terminate their motion behavior -- rectangles stop rubbering, for example) to anticipate a GDK_BUTTON_PRESS event, even if you didn't ask for the bugger in your request list for gdk_pointer_grab() -- this, Ibelieve, is the essense of Mr Taylor's "two-line fix"advise. He was speaking figuratively. Of course. 1.3 is another matter. When XInput dust settles down o'er Gimpland, #10498 may no longer be an issue. One hopes. Be good, be well Garry.
