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 557737 - Possible bug in antialiase filter (memory corruption?)
Possible bug in antialiase filter (memory corruption?)
Status: RESOLVED DUPLICATE of bug 51547
Product: GIMP
Classification: Other
Component: General
2.6.1
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2008-10-24 12:23 UTC by Werner Höhrer
Modified: 2008-10-24 19:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
progress of destroyed image (1.32 KB, application/zip)
2008-10-24 12:30 UTC, Werner Höhrer 		Details

Description Werner Höhrer 2008-10-24 12:23:47 UTC 
I just came by this recently when playing around with some of the filters in Gimp - This procedure is not really something I use on a regular basis :)

Steps to reproduce:
* Create a new white image (any non-black image should show the problem I think)
* Filter->Enhance->Antialiase
* Press [Ctrl][F] to repeat the filter A WHOLE LOT of times (i.e. just hold it down)

After some iterations suddenly black parts appear on the image which get bigger (from top to bottom).
I've tried to test this a few other times and simply got a crashed Gimp, so I guess there is some memory corruption going on here.

My Setup:
GIMP 2.6.1
Windows XP Professional SP2
Pentium 4 / 2.40GHz / 1GB RAM

Werner
Comment 1 Werner Höhrer 2008-10-24 12:30:45 UTC 
Created attachment 121264 [details]
progress of destroyed image

I've attached a few images from the color-changes (from the non-crash tests) that are applied to the images by this procedure. If one uses a non-white image all the white parts are still the original color(s).
Comment 2 Sven Neumann 2008-10-24 19:42:45 UTC 
The problem here is simply that you are running multiple antialias operations concurrently. 

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