GNOME Bugzilla – Bug 79163
Gimp crashes when trying to scale down
Last modified: 2004-03-22 16:23:25 UTC
Gimp crashes immediatly after trying to scale image down, doesn't matter what type of image or how much to scale, lets to scale upwards though. I used freeBSD ports collection to download and compile Gimp, it didn't give any compile-time errors.
Your bug-report is missing some worthwhile information. Could you tell us how you try scale the image? Please give us a step-by-step explanation of what you are doing so that we can try to reproduce the problem. I'd also like to know the version numbers and origin of the glib/gtk+ libraries you are using. Last, but not least, please start gimp from the console using the "--enable-stack-trace always" command-line option. If you get a stack trace from your crash, please include it with the bug-report.
Created attachment 7808 [details] output from --enable-stack-trace
I used menu option from Image -> Scale Image... (Shift+I), it only crashes when I change Pixel Dimensions down (i tryed today some more and seems that it doesn't crash when i leave ratio unlocked and change only Y axis, bug only occurs when i change X or both). There are gtk-1.2.10_4 and glib-1.2.10_5 packages in my freeBSD system and in /usr/ports/distfiles is gtk+-1.2.10.tar.gz. I only used "cvsup" to update ports and "make install" to compile gnome and gimp, I haven't downloaded any of the files manually. P.S added output from the stack trace as an attachment to this thread earlier today.
Thanks. The stack trace is interesting because it shows that the error occurs inside the GIMP and not inside glib or gtk. But unfortunately, the list of parameters is not shown in the trace. I do not know how much time you can spend investigating this, but it would be nice if you could recompile the code with debugging options enabled so that the parameters can be displayed correctly in the stack trace. By the way, I think that the call to "help_about_cmd_callback" just before "resize_scale_implement" is a bit suspicious.
The reporter has provided enough information so that we can reopen this bug-report.
If it's been reopened and a stack trace was added, it probably ought to be marked NEW as well. Doing so...
With version 1.2.3 and FreeBSD 4.7-STABLE I can't reproduce it. It was with a simple image (TIFF format for the file) in RVB mode without alpha channel or layers. Does the reporter can give others details?
This might be a similar problem as the one reported in bug #104693. Could the bug reporter please tell us what compiler flags he/she was using?
Changed target milestone of several bugs to 2.0 - these are not features, and don't look to me like blockers for a pre-release, but they have to be addressed before 2.0. Dave.
Created attachment 21320 [details] gdb backtrace of this problem on a debian woody i386 system
This looks a lot like a dupolicate of bug #104693. Would the reporter (or the poster of the last backtrace) please try with version 1.2.5 and report back?
Has anyone reproduced this on the 1.3 branch? While we're waiting for an answer, I'll change the target milestone to 1.2.6. Dave.
Since I made that backtrace I've upgraded from Woody to Sid. The problem seems to have gone away. I'm using gimp 1.2.5 now -- I'll try rebuilding the version I had before, and see if the bug resurfaces.
It's gone in the old version too. I guess it must be a lib.
Good to know that the problem is solved for Debian. If both the new and old versions work now, then the problem could have been related to some libraries or build tools and not to the GIMP itself. But what about FreeBSD, which was the OS of the original bug report? Could the reporter check if FreeBSD is still affected by this problem?
We are about to release 2.0 and we will not put any further efforts into gimp-1.2 development. Since several people reported this to be fixed, I will now close this report as FIXED.