Gimp consistently crashing on startup

[Pancake]

(10-25-2017, 06:19 AM)Ofnuts Wrote: A file, that's weird. Can you remove the profile start Gimp, wait for the crash, and zip the contents of the profile and attach them here (or put them on some box service and PM me the URL)?

Sure thing.  Here ya go.

[Ofnuts]

Ony two brushes in the tags.xml file. What happens if you remove the profile, and start Gimp with "gimp --no-data"? Any better (of course you won't have any brush/pattern, etc....)?

[Pancake]

(10-25-2017, 07:57 PM)Ofnuts Wrote: Ony two brushes in the tags.xml file. What happens if you remove the profile, and start Gimp with "gimp --no-data"? Any better (of course you won't have any brush/pattern, etc....)?

How would I go about starting Gimp with no data?  Apologies for my ignorance.

[Ofnuts]

You just add the parameter "--no-data" to the Gimp command. Rich explained it here:
https://www.gimp-forum.net/Thread-Gimp-C...37#pid2837

[Pancake]

(10-25-2017, 11:45 PM)Ofnuts Wrote: You just add the parameter "--no-data" to the Gimp command. Rich explained it here:
https://www.gimp-forum.net/Thread-Gimp-C...37#pid2837

Sorry once more, but how do I open Gimp-(version)-std-properties to be able to access the command line?  Sorry for being such a pain, I know the solution is probably stupidly easy.  I looked around online but couldn't find much.

[Ofnuts]

(10-27-2017, 07:40 PM)Pancake Wrote:

(10-25-2017, 11:45 PM)Ofnuts Wrote: You just add the parameter "--no-data" to the Gimp command. Rich explained it here:
https://www.gimp-forum.net/Thread-Gimp-C...37#pid2837

Sorry once more, but how do I open Gimp-(version)-std-properties to be able to access the command line?  Sorry for being such a pain, I know the solution is probably stupidly easy.  I looked around online but couldn't find much.

This isn't in the Gimp executable itself, but on the shortcut to it. If there is no shortcut, create one (but the installation will likely have created one).

[Pancake]

(10-27-2017, 08:18 PM)Ofnuts Wrote: This isn't in the Gimp executable itself, but on the shortcut to it. If there is no shortcut, create one (but the installation will likely have created one).

Yes, I have a shortcut, although it doesn't open this prompt.   It simply attempts to start the program.  Either there's some disconnect here due to a difference in operating systems, or I'm just missing something that's right in my face.

[Ofnuts]

If you have the shortcut you should be able to edit it by right-click and "Properties" or some such. Then look for a "Command" tab (IIRC).

[Pancake]

(10-27-2017, 11:02 PM)Ofnuts Wrote: If you have the shortcut you should be able to edit it by right-click and "Properties" or some such. Then look for a "Command" tab (IIRC).

Gah, sorry about that...  Alright, I added --no-data in the command line, after deleting the gimp profile, and it still crashes in the same way as before.  However, I did notice a new file in my gimp folder titled "AppCrash" with a log...


Version=1
EventType=APPCRASH
EventTime=131536055914556070
ReportType=2
Consent=1
UploadTime=131536055965141844
ReportStatus=268435456
ReportIdentifier=8eee7683-f809-474e-9d02-3eb93454dbb6
IntegratorReportIdentifier=38c1495c-93c0-4bac-b3bb-2b4e09a58bcf
Wow64Host=34404
NsAppName=gimp-2.8.exe
AppSessionGuid=00001aec-0001-0012-c101-bc74584fd301
TargetAppId=W:00066ae7ab94fee726c9fef6a1ffc4a78e0100000904!00001d8439040b15d6e29ec23814c13b08f599a1f4da!gimp-2.8.exe
TargetAppVer=1970//06//03:00:10:40!54730a!gimp-2.8.exe
BootId=4294967295
TargetAsId=2271
Response.BucketId=e5c0d0003ac824e79547626e205b72e2
Response.BucketTable=4
Response.LegacyBucketId=120832539197
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=gimp-2.8.exe
Sig[1].Name=Application Version
Sig[1].Value=2.8.22.0
Sig[2].Name=Application Timestamp
Sig[2].Value=00c9b800
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_d90f
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.15063.608
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=8274fd8b
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_8B_FROM_ntdll+0x00000000000A5EF4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.15063.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=d90f
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=d90f56af48e9a7024e8faa9acc330202
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=1ad8
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=1ad89cd2ca6cb36624fa4dd7cc9f0110
UI[2]=C:\Program Files\GIMP 2\bin\gimp-2.8.exe
UI[3]=GNU Image Manipulation Program has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\GIMP 2\bin\gimp-2.8.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[5]=C:\WINDOWS\System32\USER32.dll
LoadedModule[6]=C:\WINDOWS\System32\win32u.dll
LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll


I'm not sure if any of this information is relevant, but it's there in case it is.

[Ofnuts]

Have a look at this: https://social.technet.microsoft.com/For...progeneral

It seems Gimp trips a system protection (StackHash). But if it really did, you would be far from alone.