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 760137 - Gimp won't start up. (likely due to SSE3 requirement on 32-bit Windows systems)
Gimp won't start up. (likely due to SSE3 requirement on 32-bit Windows systems)
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Windows Installer
2.8.16
Other Windows
: Normal normal
: 2.8
Assigned To: GIMP Bugs
Jernej Simončič
: 759087 762050 765826 774194 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-01-04 23:41 UTC by Keatah
Modified: 2017-02-10 09:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test.c to compile in pow.o and strtod.o, looking for FISTTP (256 bytes, text/plain)
2016-10-08 02:27 UTC, Edward E.
Details

Description Keatah 2016-01-04 23:41:01 UTC
I also have the same problem as the OP on an XP sp3 machine. Crashes just right after parsing parasiterc and Loading "brush factory" data.

Did the usual steps like trying it on a different rig, uninstalling and manually removing all traces in the documents and settings folders..

Reverting to 2.8.14 fixes the issue. So something was broken between .14 and .16 to cause this.

http://gimpforums.com/thread-2-8-16-0-crashing-on-startup
Comment 1 Michael Schumacher 2016-01-05 09:48:02 UTC
Let's have this investigated by Jernej - if this turns out to be a major issue, then maybe it is time to reduce the list of supported platforms by one.
Comment 2 Jernej Simončič 2016-01-05 11:15:29 UTC
GIMP 2.8.16 runs fine for me on XP SP3 (I tested before release, and I just double-checked now). I also found a Pentium 4 with XP to test GIMP on, and it worked fine.

Since the report there mentions "Processor x86 Family 6 Model 13 Stepping 8 GenuineIntel ~1862 Mhz", it's possible that some component GIMP 2.8.16 ships with requires SSE3 (which the P4 I tested with supports, but the mentioned CPU doesn't).
Comment 3 Michael Natterer 2016-01-05 12:36:57 UTC
Can you attach the output of the startup with

gimp --verbose

please? This way we can see where exactly it stops.
Comment 4 Keatah 2016-01-05 15:37:08 UTC
Yeh..

::BEGIN::

It appears that you are using GIMP for the first time.  GIMP will now create a f
older named 'C:\Documents and Settings\xxxxxxx\.gimp-2.8' and copy some files to it.

Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8'...
Copying file 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gtkrc' from 'C:\Program
Files\GIMP 2\etc\gimp\2.0\gtkrc'...
Copying file 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\menurc' from 'C:\Program
 Files\GIMP 2\etc\gimp\2.0\menurc'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\brushes'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\dynamics'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\fonts'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gradients'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\palettes'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\patterns'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\tool-presets'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\plug-ins'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\modules'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\interpreters'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\environ'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\scripts'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\templates'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\themes'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\tmp'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\curves'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\levels'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\fractalexplorer'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gfig'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gflare'...
Creating folder 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gimpressionist'...
INIT: gimp_load_config
Parsing 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\unitrc'
Parsing 'C:\Program Files\GIMP 2\etc\gimp\2.0\gimprc'
Parsing 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gimprc'
gimp_composite: verbose=no
Processor instruction sets: +mmx +sse -sse2 -3dnow -altivec -vis
Adding theme 'Default' (C:\Program Files\GIMP 2\share\gimp\2.0\themes\Default)
Adding theme 'Small' (C:\Program Files\GIMP 2\share\gimp\2.0\themes\Small)
Writing 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\themerc'
Trying splash 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\gimp-splash.png' ... fa
iled
Trying splash 'C:\Program Files\GIMP 2\share\gimp\2.0\images\gimp-splash.png' ..
. OK
INIT: gimp_initialize
INIT: gimp_real_initialize
INIT: gui_initialize_after_callback
INIT: gimp_restore
Parsing 'C:\Documents and Settings\xxxxxxx\.gimp-2.8\parasiterc'
Loading 'brush factory' data
(Type any character to close this window)

::END::

I also saved the process information from the error report contents file if needed. 24f7_appcompat.txt I'll post it if needed.
Comment 5 Jernej Simončič 2016-01-05 15:46:02 UTC
OK, this is almost certainly SSE3 issue - I managed to test on an Athlon64 3000+ (no SSE3 support), and 32-bit GIMP crashes (but interestingly enough, 64-bit GIMP works fine).
Comment 6 Michael Schumacher 2016-02-01 11:12:56 UTC
*** Bug 759087 has been marked as a duplicate of this bug. ***
Comment 7 Mike 2016-02-01 17:48:02 UTC
Perhaps not relevant but nobody commented on Bug 759097 where I said, "I am now running Igor Pavlov build named File Version 9.20 gimp-stable-i686-2015-12-28.exe 2.8.17 and that works correctly."
Comment 8 Krzysztof Blachnicki 2016-04-26 23:11:49 UTC
Hello! I encountered the same behavior. I was able to find detail which "fixes" it. It happened suddenly on Windows 7 32-bit with the newest version of Gimp. It was working, nothing was added/installed/changed and next run - doesn't work. The CPU is Pentium 4 2.8 GHz or 3.0 GHz. 

I managed to fix it by deleting all brushes. Then I was adding my own, one by one and I found out that it started to crash when I added brush with hardness 1.00000. When I changed it to 0.999999 I was able to run it. Maybe somebody with such problem could try to reproduce it. Remember to temporarily move brushes from profile dir and app dir. If my findings are true, then Gimp should run with 'no data' parameter - "gimp-2.8.exe -d".

I don't have a direct access to that PC right now, but I can remotely do some debugging, if you would wish it.
Comment 9 Michael Schumacher 2016-05-03 13:46:46 UTC
*** Bug 762050 has been marked as a duplicate of this bug. ***
Comment 10 Michael Schumacher 2016-09-24 21:23:57 UTC
*** Bug 765826 has been marked as a duplicate of this bug. ***
Comment 11 Keatah 2016-09-24 21:50:53 UTC
FYI. This problem still remains in 2.8.18
Comment 12 Edward E. 2016-10-08 02:27:53 UTC
Created attachment 337210 [details]
test.c to compile in pow.o and strtod.o, looking for FISTTP

Same issue here on a Dell Inspiron B130 with XP SP3 and Celeron M 370 "Dothan". I've been looking at this on and off for about a month, and finally tracked it down. I think it can be fixed for 2.10.

Whoever makes the official Win32 builds had/has FISTTP in their 32-bit libraries as compiled by 'GCC: (Gentoo 4.9.3 p1.0, pie-0.6.2) 4.9.3'; specifically, pow() and strtodg() (as called by strtod()). The problem is that FISTTP, although an FPU instruction, is part of SSE3 per Intel. Maybe there was confusion in GCC 4.9 about when not to use FISTTP based on processor level build flags (compare https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18668); or the libs were built to local spec? Anyway, it looks like the libraries need to be recompiled, maybe with -march=pentium3.

If you compile the attachment with gcc as if building GIMP 2.10 and run it with an integer exponent argument (e.g. 'gcc -o test test.c && ./test 1.732 2.0'), and if FISTTP is still in the libs, it will crash on anything without SSE3. If you want to post the compiled binary (or even just your current pow.o) I don't mind taking a look at it to see if this is still a problem.

More info and workarounds for this bug if anybody wants it.
Comment 13 Michael Schumacher 2016-10-08 08:35:47 UTC
Thanks Edward, this is exactly the kind of effort and contribution we need from users of affected platforms in such cases.
Comment 14 Michael Natterer 2016-10-08 09:53:24 UTC
I second that, can we keep you? :)
Comment 15 kerum 2016-11-05 16:45:57 UTC
I'm facing the same problem with dump during start of GIMP 2.8.18 after installation on Windows XP SP3 (AMD Athlon 64 Processor 3000+ 2.01 GHz 3,00 GB RAM). Here output from start with option --verbose:

INIT: gimp_load_config
Parsing 'C:\Documents and Settings\xxxxx\.gimp-2.8\unitrc'
Parsing 'C:\Program Files\GIMP 2\etc\gimp\2.0\gimprc'
Parsing 'C:\Documents and Settings\xxxxx\.gimp-2.8\gimprc'
gimp_composite: verbose=no
Processor instruction sets: +mmx +sse +sse2 -3dnow -altivec -vis
Adding theme 'Default' (C:\Program Files\GIMP 2\share\gimp\2.0\themes\Default)
Adding theme 'Small' (C:\Program Files\GIMP 2\share\gimp\2.0\themes\Small)
Writing 'C:\Documents and Settings\xxxxx\.gimp-2.8\themerc'
Trying splash 'C:\Documents and Settings\xxxxx\.gimp-2.8\gimp-splash.png' ... failed
Trying splash 'C:\Program Files\GIMP 2\share\gimp\2.0\images\gimp-splash.png' ... OK
INIT: gimp_initialize
INIT: gimp_real_initialize
INIT: gui_initialize_after_callback
INIT: gimp_restore
Parsing 'C:\Documents and Settings\xxxxx\.gimp-2.8\parasiterc'
Loading 'brush factory' data

This is fresh installation and all subdirectories in C:\Documents and Settings\xxxxx\.gimp-2.8\ are empty

Windows signature of the error: AppName: gimp-2.8.exe, AppVer: 2.8.18.0, ModName: gimp-2.8.exe, ModVer: 2.8.18.0, Offset: 00348c13

GIMP starts ok only if called with option --no-data

Let me know if you need more details
Comment 16 Michael Schumacher 2016-11-07 14:14:03 UTC
Comment 12 provides everything we need to know, actually. From here, it is a packaging issue, and thus set to the Windows installer component.
Comment 17 Michael Natterer 2016-11-10 23:08:22 UTC
*** Bug 774194 has been marked as a duplicate of this bug. ***
Comment 18 Michael Schumacher 2017-02-09 23:05:12 UTC
We got reports that this issue is gone with the installer for GIMP 2.8.20. Resolving as fixed.
Comment 19 Keatah 2017-02-10 09:49:13 UTC
Yes it seems to work fine now. Thanks for the fix!