After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 302822 - Bucket fill and large random selection causes crash
Bucket fill and large random selection causes crash
Status: RESOLVED DUPLICATE of bug 149616
Product: GIMP
Classification: Other
Component: Tools
2.0.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-05-03 09:43 UTC by Nick Smith
Modified: 2005-05-04 20:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nick Smith 2005-05-03 09:44:18 UTC
Here's the process to reproduce the problem:

1.  Using Photostudio 2.0, create a new image that is 1024x1024.
2.  With a pure-white background, use the add noise feature with a setting of at
least 50 and okay it.
3.  Use the color reduction option and set the RGB channels to 2 to create a
randomized mess of 8 different colors.
4.  Save the image as a BMP file.
5.  Open the GIMP and the file you just saved.
6.  Add an alpha channel to the image.
7.  Use the select-by-color tool and choose any color.
8.  Choose the bucket fill tool, and click on the image.

At this point, an error occurs saying something of a stack fault.  No matter how
you do it, you'll always get this error and it mainly happens with large images.
 I also tried to select half of the image with the rectangular select tool then
intersecting a color selection to reduce the number of colors visible, but I
still get the error.  It doesn't happen with 512x512 images, though the program
runs very slowly (taking about 5 or so seconds to react).  I have a sample of
something to help you understand what I mean and test it yourself.  Because
random things don't compress well, the file size is rather large.  You can
download my sample at http://www.ulillillia.us/temporary/randommess.zip (about
460 KB).
Comment 1 Sven Neumann 2005-05-03 11:05:24 UTC
What version of gimp are you using? Please fill in the version field.
Comment 2 Nick Smith 2005-05-04 06:12:33 UTC
I was using version 2.0 when I encountered the error.  When I updated to the
latest version supporting Windows 98 SE, the GIMP would take even a minute just
to switch tools when viewing at 4x magnification on that same image I've
provided as a sample.  It might be because the tile size thing is at 128 MB
instead of 64 as the default was with 2.0.  I've left everything at the default
except the checkerboard size for transparent things (just made it smaller).  The
error doesn't occur with 2.2.6, but the program is extremely slow taking ages
just to switch tools or change the settings of the tools (such as adjusting the
opacity).  With the selection active, I can see that the outline is animating at
a normal speed which could be the cause for the slow speed, but unsure of it.
Comment 3 Michael Schumacher 2005-05-04 13:35:23 UTC
So the original problem is fixed?

I can't reproduce the slowness problem on my 98 SE test system. To research this
further, it would be best to open a new report, as the first comment of this one
will lead any reader to the wrong issue.
Comment 4 weskaggs 2005-05-04 14:59:30 UTC
It might be helpful to know what kind of computer you are using (processor and
speed), and how much RAM it has.
Comment 5 Nick Smith 2005-05-04 19:51:02 UTC
When I was trying to make clouds for my game, a cloud texture of 1024x1024 with
varying transparency of white, I got this error.  It's as if the GIMP can't
handle large random selections.  I wasn't getting it with that test file either,
so I went and created some more test files to see how to reproduce it.  The more
random the selection is and the more dense it gets, the more likely I'll get the
error.  The first sample doesn't provide a big enough selection no matter how
you use it.  So, here are two more samples (in one ZIP file) in which I
encountered problems with.

http://www.ulillillia.us/temporary/GIMPproblemsamples.zip (520 KB download)

The first one, the one without the number made GIMP almost nonresponsive.  When
I used the select-by-color tool at 0,20 and tried to click on any of the tools,
they didn't respond and it took nearly 20 seconds for the GIMP to change to the
window containing the tools (the tool images) and when I clicked on a tool, even
two minutes later, the tool wasn't selected as it was still on the select by
color tool.  While the tool was trying to be selected, the selection border
animations were playing at almost full speed with occasional pauses.  The
animation stuff is hogging up processor power when, if the window is inactive,
the animation should stop to allow for better processor usage.  I had to use
control+z to get rid of the selection, then switch to the tool I need to use,
redo the selection, then apply the tool.

The second one (the one with a number) produces an error, a runtime error, but
not the original error I encountered.  When I used the select-by-color tool on
either the black or white on this one, I'd get an error saying it failed to
allocate 13 million something bytes.  Click okay then it says that a runtime
error has occurred.  Click okay and the GIMP closes.  I got some screenshots of
these errors:

http://www.ulillillia.us/temporary/GIMPerrorscreenshots.zip (190 KB download)

What I don't get is how can a selection use up more than 13 million bytes of
memory?  The problem is worse when the single pixels are in a checkerboard pattern.

My computer specs (detailed):
OS = Windows 98 SE;
RAM = 512 MB; // I believe it's DDR RAM, 400-something MHz bus speed
HDD = 16 GB with 9 GB free; // going on 5 1/3 years old
Video = Radeon 9600 XT; // 128MB memory, with 500 MHz core, 600MHz memory clock
Monitor = 18 inch diagonal; // it's brand new and looks like a TV
Display = 1600x1200 at 32-bit color; // the reason for getting the new monitor
was for the high resolution
CPU = AMD 1.05 GHz Duron; // would like to upgrade to about 2.0 GHz but don't
know if motherboard supports it or not
Motherboard = K7VTA3 version 6.0; // don't know how recent this is nor it's
specifications (lost the original box)
Comment 6 Sven Neumann 2005-05-04 20:17:03 UTC

*** This bug has been marked as a duplicate of 149616 ***