PLEASE HELP!!!

You got to help us to help you - what are you doing when this happens?

I can leave and did the GIMP running without any open graphic's for 2-3 days and it was fine, it's only when I work with multiple images does it crash. I've tried to narrow down where the GIMP keeps it's temporary cache of recent documents I have it tracked down to a file but that doesn't help me.

I'm an I.T. Specialist of 19year's; so please tell me what I need to provide further; I'm thinking of trying to utilize portable gimp or downgrading for the time being because I'm on a deadline which means if I don't get this done I am dead.

God Bless All Of You!!!
-meb

Yes I'm an advocate of the Portable Application Development of the future so I decided to utilize a program by the name of CAMStudio to record the happening's of the everyday life before the GIMP Crash's; I have a unlimited hosting on my WEB Hosting provider I'll post the results their ASAP when and if it happens again.

-meb

Please note that Camstudio is known to interfere with some of GIMP's ui - namely drag&drop.

I'm having this same problem. I'm a basic user and I'm using GIMP to just do basic manipulation. I was using 2.4 for the longest time and then upgraded. After upgrading this issue started happening.

I'm using Windows 7 x64 Ultimate SP1 and I can't recreate it as one basic function that seems to be happening. What I am doing is copying portions of pictures and creating their own picture in another window and then cleaning it up with eraser tools and paintbrushes.

This is a copy of the crash from my Event Viewer

Log Name:      Application
Source:        Application Error
Date:          04/03/2015 12:50:47
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Earth
Description:
Faulting application name: gimp-2.8.exe, version: 2.8.14.0, time stamp: 0x00000000
Faulting module name: libcairo-2.dll, version: 0.0.0.0, time stamp: 0xa340a328
Exception code: 0xc0000005
Fault offset: 0x0000000000023601
Faulting process id: 0x4824
Faulting application start time: 0x01d056bb1200a076
Faulting application path: C:\Program Files\GIMP 2\bin\gimp-2.8.exe
Faulting module path: C:\Program Files\GIMP 2\bin\libcairo-2.dll
Report Id: 21cc0866-c2b0-11e4-993d-001cc030b4ca
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-04T20:50:47.000000000Z" />
    <EventRecordID>109756</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Earth</Computer>
    <Security />
  </System>
  <EventData>
    <Data>gimp-2.8.exe</Data>
    <Data>2.8.14.0</Data>
    <Data>00000000</Data>
    <Data>libcairo-2.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>a340a328</Data>
    <Data>c0000005</Data>
    <Data>0000000000023601</Data>
    <Data>4824</Data>
    <Data>01d056bb1200a076</Data>
    <Data>C:\Program Files\GIMP 2\bin\gimp-2.8.exe</Data>
    <Data>C:\Program Files\GIMP 2\bin\libcairo-2.dll</Data>
    <Data>21cc0866-c2b0-11e4-993d-001cc030b4ca</Data>
  </EventData>
</Event> 

Is there anything else I can do to help figure this out?

Created attachment 332421 [details]
2.8.18 crashes on startup on XP. Not sure this is related

Not sure this is related to this bug.

On Comment #7 I tried to attach an image to further clarify the details. It didn't worked out. I uploaded the 3 related images to http://imgur.com/a/QRK3z

Regarding Comment #7 and Comment #8:
I had the same issue with http://portableapps.com/apps/graphics_pictures/gimp_portable GIMPPortable_2.8.18, GIMPPortable_2.8.16-4, GIMPPortable_2.8.16. GIMPPortable_2.8.14-fix, however, is launched successfully.

Regarding Comment #7 and Comment #8 and Comment #9:
Forgot to mention my XP SP3 is a 32 bits machine.

Created attachment 332439 [details]
The full error file that XP created for 2.8.18

Regarding Comment #7, #8, #9, #10:
After Uninstalling upstream's 2.8.18 I realized that the 3rd, bottom, image I uploaded in #8 to http://imgur.com/a/QRK3z has a file name which might be of interest. I reinstalled it. The content of the resulting file is attached. The attached file has a slight different name. Hopefully, the important content is the same.

ronvarburg, do you know if your platform supports SSE3? Have a look at bug 760137.

IF SSE stands for Streaming SIMD Extensions than my CPU only supports SSE. It doesn't support SSE2, Neither SSE3.

Comment #13 was a reply to comment #12. Is it a not enabled JavaScript issue that caused the reply button not to add that information?

Michael Schumacher, on comment #12:
The only other words I can write is that LibreOffice confronted the SSE issue in the past. I think it was around LibreOffice 5.0 version. To the best of my knowledge, they solved it, or most of it, and currently allow old CPUs to run LibreOffice on XP. I think they developed some tools to locate the points where the issue hits, and bypass the advanced SSE requirement. 
I hope this is a meaningful, and helpful, comment.

Rethinking, in addition to what I wrote on comment #15:
1. Bug 82430 – LO 4.3.0 for Windows crashes on CPUs that do not support SSE2: Application Error soffice.bin, version 4.3.0.4, module sal3.dll, version 4.3.0.4, address 0x000268d5. at https://bugs.documentfoundation.org/show_bug.cgi?id=82430
2. I think that one thing that LO was, perhaps still, doing is trapping the issue in their application, popping the end user an explicit message whenever the SSE issue hits him.

We think that the SSE3 dependency might be in some library.

However, few of us use the Windows platforms at all, and if we do, then more current versions - it will be hard for us to pin it down without help from people who are affected by the issue.

(In reply to Michael Schumacher from comment #17)
> We think that the SSE3 dependency might be in some library.
> 
> However, few of us use the Windows platforms at all, and if we do, then more
> current versions - it will be hard for us to pin it down without help from
> people who are affected by the issue.

Are you sure it is an SSE3 dependency problem? On my machine it might also end in SSE2.
How can I help? Is there any --debug, or similar option, that is usually not employed by end users? If there is, how can I activate it? Any other method?

(In addition to my comment #18)
Is there something similar to https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg, assuming it might help here too? I think https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg is concentrated in LibreOffice. For example, it mentions CACHE*C:\symbols;SRV*http://dev-downloads.libreoffice.org/symstore/symbols;SRV*http://msdl.microsoft.com/download/symbols.

So... the initial bug report got diverted (as of comment 7) into another issue issue that is handled in bug 760137.

I think we also got a report for the cairo crash already.

Does *the original issue* still happen with 2.8.20?

Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!