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 331094 - gimp crash when a little bit big image is made
gimp crash when a little bit big image is made
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: General
2.2.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-02-14 07:14 UTC by Byeong-taek Lee
Modified: 2008-01-15 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Byeong-taek Lee 2006-02-14 07:14:20 UTC
Please describe the problem:
gimp crash when i make a big image.
small sized image is ok, but a given sized image make gimp crash.
for example, when i make a 1280x768 image, it works fine.
but when i make a new image of 1280x480, it crashes.

Steps to reproduce:
1. run the gimp
2. make new figure with image size of 1200x400
3. crash


Actual results:
(script-fu:26419): LibGimpBase-WARNING **: script-fu: wire_read(): error


Expected results:
as usually, it should show a new blank image.

Does this happen every time?
always, but with some sized image

Other information:
This crash doesn't occur when i use other laptop or desktop, of which display
resulution is 1024x768 or 1600x1200.
But when i use another laptop with non-standard display size such as 1280x800,
it crashes.
Actually, i have tried to change some parameters in resolution at preferences,
but it didn't help.
My platform is gentoo x86 (not experimental, but stable).
If you need other information to fix the problem, let me know it.
Thanks.
Comment 1 Manish Singh 2006-02-14 07:25:09 UTC
Please try with 2.2.10, bug reports against older versions aren't really that useful. And if it still happens with 2.2.10, provide a stack trace, and make sure the gimp binary has debugging symbols.

Also, since you're using Gentoo, please verify you aren't using insane CFLAGS. "Stable" gentoo doesn't mean anything.
Comment 2 Byeong-taek Lee 2006-02-14 07:31:11 UTC
I tried gimp 2.2.10 right now, but no change.
When i change the screen resolution from 1280x800 to 1024x768 on the same machine,
gimp works fine.
My CFLAGS="-march=pentium-m -mtune=pentium-m -Os -pipe -mmmx -msse -msse2 -mfpmath=sse -falign-functions=64"
but ebuild file filter out some options such as -Os.
Comment 3 Manish Singh 2006-02-14 07:49:45 UTC
And the stack trace?
Comment 4 Byeong-taek Lee 2006-02-14 08:35:22 UTC
I'm sorry, I have no debug useflags.
Actually, I have recompiled gimp with debug information,
but gdb told me that the program has no debugging symbols found except following messages.

---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1217697216 (LWP 3622)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1217697216 (LWP 3622)]
0x080a2a46 in ?? ()

I wonder if it helps you.
To get any debug information, i think that i re-emerge everything from glibc.
However, it will take so long time.
Comment 5 Manish Singh 2006-02-14 08:43:04 UTC
The above is not helpful.

Please build from glib on up with only -O2 -pipe and see if it makes a difference.
Comment 6 Byeong-taek Lee 2006-02-14 08:56:55 UTC
wow,
After i reemerge glib with only -O2 -pipe,
gimp works fine!
Thank you very much.
Comment 7 Raphaël Quinet 2006-02-14 11:28:30 UTC
The problem was most likely due to incorrect optimization flags used when
compiling glib, so this was not a GIMP problem.  Closing this bug report.