GNOME Bugzilla – Bug 759087
Gimp Crash On Startup
Last modified: 2016-09-25 03:35:49 UTC
Created attachment 316839 [details] Error Report File I had a working Gimp version 2.8.14. After I replaced that installation with version 2.8.16 I found that Gimp crashes as soon as it start up. Attached is the error report that was generated when it crashed. My operating system is Windows XP. I am going to revert to version 2.8.14.
I installed 2.8.16 and experienced exactly the same problem. The message is "GNU Image Manipulation Program has encountered a problem and needs to close." My operating system is also XP and has the latest updates from Microsoft. My system is a dual processor XEON @ 1.7 Ghz. I did have a prior version of GIMP that worked (several years old).
I have experienced the same problem with Windows 7. Details of error are these: Nombre del evento de problema: APPCRASH Nombre de la aplicación: gimp-2.8.exe Versión de la aplicación: 2.8.16.0 Marca de tiempo de la aplicación: 00000000 Nombre del módulo con errores: gimp-2.8.exe Versión del módulo con errores: 2.8.16.0 Marca de tiempo del módulo con errores: 00000000 Código de excepción: c000001d Desplazamiento de excepción: 00348863 Versión del sistema operativo: 6.1.7600.2.0.0.256.1 Id. de configuración regional: 3082 Información adicional 1: 0a9e Información adicional 2: 0a9e372d3b4ad19135b953a78882e789 Información adicional 3: 0a9e Información adicional 4: 0a9e372d3b4ad19135b953a78882e789
I don't see anything relevant in the "report file". Is there anyone able to get a backtrace of the crash? I read the gdb can be used on Windows as well. If you could install it, here is a procedure to get the trace: https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_trace_using_GDB
I followed the link you provided. In the document you linked to I attempted to follow the "GettingTraces/DistroSpecificInstructions" link to find out what I need to install, and found that link broken. It went to a page with the message: "This page does not exist yet. You can create a new empty page, or use one of the page templates."
GDB requires MinGW and MSYS be installed. On page: http://www.mingw.org/ The DOWNLOAD button to the upper right is a link to: http://sourceforge.net/projects/mingw/files/latest/download?source=files I will no longer install anything downloaded from Source Forge for this reason: http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/
I got feedback from the MinGW developer that they have not opted into Source Forges Devshare. They claimed there is no adware or malware wrapper. So I downloaded the installation files and scanned them with both SuperAntiSpyware and BitDefender. Both results were negative. So I installed them. Pasted below is the GDB output: $ gdb 'C:/Program Files/GIMP 2/bin/gimp-2.8.exe' GNU gdb (GDB) 7.6.1 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from C:\Program Files\GIMP 2\bin\gimp-2.8.exe...(no debugging sy mbols found)...done. (gdb) run Starting program: C:/Program Files/GIMP 2/bin/gimp-2.8.exe [New Thread 5676.0x1664] [New Thread 5676.0x6b0] [New Thread 5676.0x768] Program received signal SIGILL, Illegal instruction. 0x00748863 in ?? () (gdb) thread apply all bt
+ Trace 235826
Thread 3 (Thread 5676.0x768)
Thread 2 (Thread 5676.0x6b0)
I installed 2.8.16 on Win XP SP3 but found on startup the program crashed when it reached the point of loading the brushes. I renamed the brushes folder and the program started; after progressive renaming of sub-folders only I discovered that just an empty folder named brushes would cause the start-up crash. I initially worked with the folder in the program files installation followed by doing the same thing in Documents and Settings with very similar results; this time a brushes folder was acceptable but sub-folders were not. If I added brushes direct into the brushes folder in Documents and Settings then the program started. I tried this on a desktop machine and a laptop and got identical results. 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.
Amazing! I just loaded 2.8.16 on WinXP-SP3 machine and had same problem as original poster: Crash at offset 00348863 with Code 0xC000001D. Just began looking and found Mike's post of barely 2 hours ago. Renaming the 'Brushes' folder in Prog Files worked for me as well. GIMP started up immediately. Timing couldn't have been better! Thanks for the short term fix, Mike.
Hi, Which "brushes" folder is it? The one from GIMP installation or from your user config directory? (if you are not sure what I mean, just give me the full path, and I'll deduct) Thanks!
Hi Jehan, My first work was with the brushes folder from the GIMP installation where even an empty folder called brushes would cause GIMP to crash on startup. My second work was with brushes in the user config directory in Documents and Settings where the presence of a sub-folder within brushes would again cause a crash on startup. I will add a crash report file above. Mike
Created attachment 318102 [details] Crash on Startup In support of my crash report that having a folder called 'brushes' causes a crash on startup.
For the record, I have tested with the development version of GIMP on a Windows 7 VM. I tried with empty brushes/ folder both in the user config directory and in GIMP installed data (even though this one should never be empty by definition, but well I tried anyway). I tried adding a subfolder in both directories as well, and still had no crash. I have not tested GIMP 2.8.16. And I have not tested on XP, which I don't have and I see most of the comments on this report are using it (all but comment 2). I'm actually not even sure that Windows XP is still supported for GIMP by the way. Do we still support it?
As I said (Comment 2) I was experiencing the same problem with GIMP 2.8.16, using Windows 7. The problem has been solved simply by renaming the folder Brushes in C:\Program files\GIMP 2\share\gimp\2.0, as suggested. Thank you Mike and others.
Well, then you have just removed a lot of GIMP's brushes from being loaded. This is no solution, it is a workaround. And it is also not a general problem, because there are no "GIMP does crash!!!" report from >90% of the users.
Sad news then. At least I can use GIMP 2.8.16 though not many brushes. I'll wait for a straight solution is worked out.
It is a better workaround once the brushes are copied into: c:\documents and settings\'me'\.gimp-2.8\brushes A downside is that I do not seem to be able to get a startup if they are in sub-folders. I can copy .gbr and .gih files without a crash but .vbr crashes it on startup. Mike
This - at least the initially reported issue - is probably the same as bug 760137. There, running GIMP on a 32 bit platform on a hardware that doesn't offer SSE3 makes it crash on start. I'm not yet convinced that this is due to something with the brushes, unless the initial reporter can confirm that the workaround mentioned in the past few comments helps there as well. Please, do not mix different issues in a bug report simply because the symptoms are the same - report them as a new bug, if we figure out they are related, we can resolve the reports as duplicateslater.
If this is really the SSE problem then crashing in brushes is plausible. When GIMP starts up, the first time it deals with pixel buffers (and thus babl) is when it loads the brushes. Unless I missed some earlier place...
Let's assume it is a duplicate of this bug. Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 760137 ***
The computer I was using when I reported this was a very old one, and so the problem very likely was due to SSE. That computer recently failed on me in a way that is beyond repair. I have updated computer hardware now, and look forward to continuing Gimp work on it.
(In reply to artist from comment #20) One more thing: I am now using Ubuntu-Studio due to Windows privacy issues. That older computer that failed's OS was Windows XP.