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 459135 - Seg-fault opening or creating an image of size 1x770 or wider
Seg-fault opening or creating an image of size 1x770 or wider
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-07-21 23:45 UTC by jsado_sc1
Modified: 2008-01-15 13:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jsado_sc1 2007-07-21 23:45:25 UTC 
If I load an image of any type (I have tried jpeg and gif) that is one pixel high and 1024 pixels wide, the Gimp segmentation faults. I have tried to create a new image that is one pixel high and various widths and have determined that I can create an image that is 767 pixels wide, but anything wider than 770 makes the Gimp segmentation fault.
Comment 1 jsado_sc1 2007-07-21 23:50:55 UTC 
After further investigation I have determined that I can not create any image that is wider than 770 pixels, not just one that is only 1 pixel tall. I do not think this is a memory issue as I have plenty of memory:

 7> free -m
             total       used       free     shared    buffers     cached
Mem:           478        445         32          0         37        194
-/+ buffers/cache:        213        264
Swap:          251         65        185

I believe this used to work.
Comment 2 jsado_sc1 2007-07-23 01:10:20 UTC 
I recompiled the Gimp (2.2.16 actually, after an upgrade simply didn't fix the problem) in order to obtain a back trace of the problem, and now the problem doesn't happen. I am suspecting that it might have something to do with my optimizations. I have been using these flags:

CFLAGS="-Os -mtune=pentium4 -msse2 -mfpmath=sse -pipe -fomit-frame-pointer"
Comment 3 Sven Neumann 2007-07-23 08:30:14 UTC 
Closing as OBSOLETE because an update seems to have fixed the problem.