Hi! What OS?

Windows Vista 6.0 sp 1

You just caught me... I was just about to go to bed. Do you need any other information at the moment?

Only that we have started to get a lot of these reports for 2.6.6 on Windows which makes me think this has something to do with an error in the Windows build process.

Jernej, could you take a look please?

where do you need me to look at?

sorry, it's 2:48 a.m. my time... I will gather the info you need later after I get some sleep. :)

Just let me know where to look, please. I'm pretty tech savvy if you give me the place where to look.

I don't need to download / install that stack trace program, do I??

Thank you for letting me know that this is something happening to others. That makes me feel better... in a way.

May I ask, (for future reference), why you changed the component from User Interface to Installer?

Jernej is a name, I asked Jernej to look at it. Now stop spamming this bug report please :O

Please forgive me, I thought you were asking me to look at something on my end.

I didn't know asking more questions about this bug was considered "spamming".

Just please, let me know if you need any other information from me. Thank you & good night.

(In reply to comment #0)

Same happens to me with GIMP 2.6.6 in Vista 64.
First, I observed the problem only when in an image with several layers. At that time, I found that if I hide all layers except the one I need to correct color, works fine. But than, since 3~4 days ago, I just can open color or color balance tool. I didn't find a work around, yet.
Also, previous release of GIMP didn't.

*** Bug 577802 has been marked as a duplicate of this bug. ***

*** Bug 579301 has been marked as a duplicate of this bug. ***

*** Bug 578886 has been marked as a duplicate of this bug. ***

Combined all the color-related crashes into one, as they do most likely have the same reason.

Last weekend I installed 64bit version for Vista (I know that it is not yet released). In this one, all those tools works fine. I just noticed some problems with menu and options hide/show (paint handlers not finished yet?).
For now, I'm successfully using 64bit version.

*** Bug 579620 has been marked as a duplicate of this bug. ***

*** Bug 576495 has been marked as a duplicate of this bug. ***

*** Bug 577377 has been marked as a duplicate of this bug. ***

Vista Home Premium SP1
Same happens to me. It crashes gimp even if no picture is loaded (open gimp without any image=> menu colours => any tool from first group=> crash).
After reinstalling it works only when GIMP is running first time. Also from time to time (1 for 7-10 runs) colors tools are working correctly. Sometimes even if gimp is working correctly it is crashing during closing (vista displays messsage: "program stoped working...").
I think that LANG variable may affecting this bug. Earlier I had this set to en_GB and gimp crashed only during using colour tools. Now, after deleting of LANG variable it also crashes during closing.

Me to with GIMP 2.6.6 in Vista 64.
Open gimp > colors > color balance and it crashes, but only with the color balance all the other tools under color work fine.

the problem I have seems to be related, opening "bightness-contrast" crashes the gimp, but other dialogs from the color window simply do not open.  I uninstalled and reinstalled and the problem persisted.  I uninstalled again and installed 2.4.7 and tried again, same problem.

I'm running Vista Ultimate SP1 32-bit but I also have a windows 2003 sp2 system which does not have any problems.

I uninstalled and reinstalled but went the custom route and chose not to install the GTK+ component and everything seems to be working fine now.

*** Bug 583359 has been marked as a duplicate of this bug. ***

*** Bug 584054 has been marked as a duplicate of this bug. ***

I have the same problem trying to open levels

*** Bug 577571 has been marked as a duplicate of this bug. ***

*** Bug 585517 has been marked as a duplicate of this bug. ***

*** Bug 582750 has been marked as a duplicate of this bug. ***

*** Bug 585702 has been marked as a duplicate of this bug. ***

This bug is never going to be fixed unless a windows user sits down and
debugs it.

*** Bug 582635 has been marked as a duplicate of this bug. ***

*** Bug 586320 has been marked as a duplicate of this bug. ***

*** Bug 586334 has been marked as a duplicate of this bug. ***

We really need a stack trace of this crash.

If you guys run gimp-2.6.exe As Administrator, does that fix the crash?

Hi,
I ran gimp-2.6.exe as Administrator and it still crashes, but only when I try to exit.  I got this crash info:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	gimp-2.6.exe
  Application Version:	0.0.0.0
  Application Timestamp:	49c4317f
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.0.6002.18005
  Fault Module Timestamp:	49e03824
  Exception Code:	c0000005
  Exception Offset:	0002ac0f
  OS Version:	6.0.6002.2.2.0.768.3
  Locale ID:	4105
  Additional Information 1:	fd00
  Additional Information 2:	ea6f5fe8924aaa756324d57f87834160
  Additional Information 3:	fd00
  Additional Information 4:	ea6f5fe8924aaa756324d57f87834160


I hope this helps.

I've had this bug when editing anything having to do with color out of the toolbar or the right click menu. I am running 2.6 on Windows Vista Ultimate OEM 64 bit. I had the problem even after I opened it as admin. If this bug cannot yet be fixed, may I recommend creating an autosave option?

I am running Vista Home Premium SP2 x64 OEM as an administrator. I still have the problem with color tools.

I am using XP Pro SP3 and the error also shows running as admin. However, lately I hadn't any problems with working with the option "Colors / Use GEGL" turned on, which I would swear that provoked crashes in the past.

Thanks for the info everyeone. Looks like running as admin doesn't have anything to do with it unfortunately.

Hi again... as the reporter of this bug, I was wondering if there is anything you need from me?

I am sorry I did not see your request about a stack trace... I had some unrelated computer issues & was not able to get to my email until today.

Anyway, please let me know if I can be of any help... Just let me know what I need to do.

Thanks, LH! :)

Well the request for a stack trace still holds.

*** Bug 587158 has been marked as a duplicate of this bug. ***

(In reply to comment #41)
> Well the request for a stack trace still holds.
> 

Ok... if you have access to my email, will you please send me the instructions on how to do this / find the log? Thanks.

(if not access to my email address... then I guess you'll have to post it here.) :)

The first step is finding a GIMP build for Windows with debugging symbols. Maybe someone of our more experienced GIMP Windows users know where to find one? I don't.

Looks like...

Step 1: get windbg - http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx

Step 2: install Gimp 2.7 or download the 2.6.6 sources and compile with debugging symbols.

This information was condensed from:
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
http://lists.xcf.berkeley.edu/lists/gimp-developer/2009-May/022321.html

I'll play with this tonight when I'm in front of my vista system.

*** Bug 587347 has been marked as a duplicate of this bug. ***

Workaround available:

If you install Gimp 2.6.6 in the Customize mode and disable the checkbox for 'MS-Windows engine for GTK+' then the crash does not occur.
This is at least valid for me with Windows Vista Home Premium SP2.

Nick has written it already in Comment #21 but it seemed to me that nobody really noticed it.

(In reply to comment #44)
> The first step is finding a GIMP build for Windows with debugging symbols.
> Maybe someone of our more experienced GIMP Windows users know where to find
> one? I don't.
> 

I'm using Vista Ultimate 64-bit SP2 and have this issue as well. After having this problem with 2.6.6 and finding this thread, I downloaded and set up the latest 2.7 build from sourceforge; the problem persists at Colors->Levels.  I haven't quite figured out how to get WinDbg to do what we want here, but I'm doing further research.  I'm no programmer; any hints would be appreciated.

Created attachment 137894 [details]
example where the crash does not occur

Created attachment 137895 [details]
example where the crash occurs

In the attachments the consistent factor is, strangely, the error fails to occur if I run the executable from the debugger, but always occurs if I run GIMP first and then attach the debugger.  Again, I'm new to this, let me know what else I can do that might be helpful.

(In reply to comment #47)
> Workaround available:
> 
> If you install Gimp 2.6.6 in the Customize mode and disable the checkbox for
> 'MS-Windows engine for GTK+' then the crash does not occur.
> This is at least valid for me with Windows Vista Home Premium SP2.
> 
> Nick has written it already in Comment #21 but it seemed to me that nobody
> really noticed it.
> 

I tried this with Windows Vista Home Premium SP1 and it crashed on the first try when selecting "Color Balance"

I was recently forced to re-install windows and I haven't been able to reproduce the behaviour I described earlier by not installing GTK+.  A friend suggested GIMPhoto, which does not appear to have this problem, so I've been using that.

(In reply to comment #52)
> (In reply to comment #47)
> > Workaround available:
> > 
> > If you install Gimp 2.6.6 in the Customize mode and disable the checkbox for
> > 'MS-Windows engine for GTK+' then the crash does not occur.
> > This is at least valid for me with Windows Vista Home Premium SP2.
> > 
> > Nick has written it already in Comment #21 but it seemed to me that nobody
> > really noticed it.
> > 
> 
> I tried this with Windows Vista Home Premium SP1 and it crashed on the first
> try when selecting "Color Balance"
> 

I had a similar result with Windows Home Premium SP1 64bit after trying the workaround. 

I was able to desaturate a color tiff file and save it successfully but GIMP crashed immediately when Gimp is closed. 

If I start Gimp again and reload the saved tiff, color tools crash the program. 

If I restart Gimp and use a color tool before I load a file then load a file the tool works, the file can be saved but again Gimp crashes when it closes and the sequence begins again.

*** Bug 588081 has been marked as a duplicate of this bug. ***

*** Bug 587857 has been marked as a duplicate of this bug. ***

Created attachment 138255 [details]
Windows Event Log entries

Comment on attachment 138255 [details]
Windows Event Log entries

I just attached two event log entries.  I hope this can help the developers locate this problem.

Comment on attachment 138255 [details]
Windows Event Log entries

For anyone looking for a workaround, I downgraded to 2.4.7 and ran GIMP without seeing the problem.  I am running Windows Vista Home Basic, SP1.  I could use the color tools of 2.6.6 with no pr5oblem, but GIMP always crashed when I tried to save.

I did a quick test of version 2.6.1. It does not seem to have the bug.
I'm running Vista Home Premium SP1 64 bit version.

*** Bug 588496 has been marked as a duplicate of this bug. ***

*** Bug 588504 has been marked as a duplicate of this bug. ***

*** Bug 588597 has been marked as a duplicate of this bug. ***

*** Bug 588948 has been marked as a duplicate of this bug. ***

There have been a report that this problem was introduced after installing KB961371, hopefully someone on Windows can investigate this closer.

The first time I encountered this bug was when I was going to colorize a layer,
and GIMP crashed. After restarting the system, GIMP won't even start.
Uninstalling GIMP and removing it's dirs then installing 2.4.x seems to be
okay.

BTW only crashed after Vista SP2 KB961371

(In reply to comment #65)

Rolling back KB961371 should have restored older versions of the dlls, but did not stop the problem with GIMP 2.7.0-git-20090507.  Are those Windbg logs of no use?  It seems odd that the OpenType font engine components would have anything to do with this.  Nothing I recognize as related in the system logs, yet.
http://www.microsoft.com/technet/security/bulletin/MS09-029.mspx

Ok :(

Your Windbg output doesn't seem useful to me but thanks anyway. To see what a stacktrace looks like, see this bug report for example: bug #587782.

I had the same problem. With open something with colors, GIMP crasched. GIMP was made for LINUX, not for Vista32. The only help is uninstall GIMP 2.6.6. and install older version, GIMP 2.4.7 .
I have no problem now !!!!!!! 

Hi,

I have the same problem on Windows Vista 64-bit :( The workaround of not installing 'MS-Windows engine for GTK+' does not prevent GIMP from crashing when you quit.

I understand GIMP developpers might favour support for Linux to the detriment of Windows, but still... this bug is really serious and was reported more than three months ago. Shouldn't priority on this be raised ? Maybe it's time there were an official Windows installer.

If I had Windows I would fix this problem right away, but I don't have Windows so I can't. I'm obviously not going to buy a Windows licence just so I can fix this bug.

This problem indeed has a higher than normal priority, raising to High

We already have official installers provided by Jernej's.

Created attachment 138771 [details]
Attached windbg after process started, reproduced crash.

  Sorry to take so long figuring this out.  The stack trace information is in the latter 3rd of the text.  There are a lot of warnings about missing symbols.  According to the following link, if I'm reading it right, this build may be missing some of the symbol info needed for a proper stack trace.  Good luck.

Ack.  Forgot the link:
http://lists.xcf.berkeley.edu/lists/gimp-developer/2009-May/022321.html

Thanks, that's actually a pretty interesting log, but unfortunately it does not have debugging symbols for gimp-2.6.

I have teamed up with Jernej and we will together try to find a solution to this problem, hopefully within the next days.

*** Bug 589203 has been marked as a duplicate of this bug. ***

*** Bug 589460 has been marked as a duplicate of this bug. ***

*** Bug 590006 has been marked as a duplicate of this bug. ***

*** Bug 590222 has been marked as a duplicate of this bug. ***

*** Bug 590476 has been marked as a duplicate of this bug. ***

I'm also experiencing this bug on the Windows 7 release candidate.  Note that this also invalidates the argument of "I'm not going to go buy Windows to fix this bug" as the release candidate is freely available.

Running the RC in VirtualBox is not a bad idea.

Setting milestone to 2.6.

This also happens on Windows XP.

*** Bug 590733 has been marked as a duplicate of this bug. ***

*** Bug 590775 has been marked as a duplicate of this bug. ***

Here is an update:

Through the mingw32 tool chain on Fedora and wine, I have fixed obviously bogus code that was introduced in GEGL right after the GIMP 2.6.4 release (see bug 589667).

My current theory is that this bogus code caused memory corruption that had a tendency to show when the color tools were invoked. This would explain why the crash doesn't consistently occur for everyone.

I'm currently trying to get this fix evaluated, will post another update as soon as I have one.

First it was the hue tool now its almost all tools crash gimp
i found 2 ways around it 1> open new gimp project and use the tool on the new then the one your working on this works 65% of the time.
2> set all tools as a shortcut this works 100% but if you go to any of the tool bars like file>save or edit or color or tools or help there is about 75% chance it will crash depending on what you select save usually is 90% crash rate for me so save first so you can fast save it using a key shortcut than work on it and avoid using the top tool bar the brushes all work fine. sometime it might random crash but it only happens 5% to 20% of the time varies depending on how much your doing at the same time-> the more you use it the higher the random crash % will be up to 85% if your a multiply picture and tool user. 5-20% is common use


-->note: use this as a Temporary fix until someone fixes the bug<--
or find another program this one is the best for what you pay for or it use-to be until all the crashes

*** Bug 587352 has been marked as a duplicate of this bug. ***

*** Bug 590973 has been marked as a duplicate of this bug. ***

Has anyone found any clue on what's going on with gimp already??
It's happening to me too, the same with the color tools but now it wont even let me save!!!! It's seriously getting on my nerves!!!
If this helps on anything, my computer is a laptop, Vista Home Premium, I have the latest version of Gimp.

This is currently believed to be a Installer build issue, i.e. not a bug in GIMP or GEGL code. We're working on it and is it quite likely that a fix will be in the 2.6.7 installer.

We have now fixed another long-standing Windows specific crash, bug 589667. I currently believe the crash reported in this bug report to be another side effect of the same issue.

Can you please try this new installer?

  http://eternallybored.org/misc/gimp/gimp-2.6.7-git-i686-setup-debug.exe

Before installing a pre-release of GIMP 2.6.7 using the above installer, remove all files in the directory

  C:\Program Files\GIMP-2.0\lib\gegl-0.0\

otherwise the crash might still be around. I have never been able to reproduce the color tools crash, that's why I need your help to judge if the above installer has the problem fixed.

If you still get a crash, please install DrMinGW so that you get a stack trace. The installer has debugging symbols in it.

  http://code.google.com/p/jrfonseca/wiki/DrMingw

Thanks!

We have now fixed another long-standing Windows specific crash, bug 589667. I
currently believe the crash reported in this bug report to be another side
effect of the same issue.

Can you please try this new installer?

  http://eternallybored.org/misc/gimp/gimp-2.6.7-git-i686-setup-debug.exe

Before installing a pre-release of GIMP 2.6.7 using the above installer, remove
all files in the directory

  C:\Program Files\GIMP-2.0\lib\gegl-0.0\

otherwise the crash might still be around. I have never been able to reproduce
the color tools crash, that's why I need your help to judge if the above
installer has the problem fixed.

If you still get a crash, please install DrMinGW so that you get a stack trace.
The installer has debugging symbols in it.

  http://code.google.com/p/jrfonseca/wiki/DrMingw

Thanks!

(Sorry for the duplicate post but bugzilla didn't seem to send mail the first time and it is really important that we get help with this)

it works so far no problems! with the new installer, and it also fixed the file-svg.exe problem no more file-svg.exe stopped working and closed window
also i ran it as the administrator when I installed it <- that might help if you installed it as the administrator. Some installer's if not run as the administrator will not install correctly I have learned that the hard way.
also clear all files from gimp before installing the new one might help too.
if you want to save anything make sure it will not affect gimp's operation like brushes. just to be safe ;)
P.S. dds plug-in works with it... for those who uses plug-in's they should still function in gimp 2.6.7
Ill post another comment if something goes wrong!

Correction: there is no need to remove any files prior to using this installer - it'll remove those files automatically.

Despite the comment that there is no need to remove any files, I installed once without removing files and the crash continued to occur, so then I removed the files from the specified directory and tried again... The crash was eliminated (at least so far).

Yeah, previously I uploaded the wrong installer. I reuploaded it a few minutes ago, and now it really doesn't need any manual file removing.

I deleted the files from the directory (it was C:\Program Files (x86)\GIMP-2.0
in my case, not C:\Program Files), installed GIMP 2.6.7 and did a test run.

So far I have had no problems.  Great going guys.

Hi, I've just uninstalled GIMP 2.6.6. to try this new installer. It fixes the crash for me too :) Thanks

Thanks a lot for the help with testing everyone, from the results there is only one conclusion that can be drawn: The problem is now fixed. Since the problems described in this bug report was fixed along with the fix for bug #589667 I am closing this as a duplicate.



*** This bug has been marked as a duplicate of 589667 ***