GNOME Bugzilla – Bug 304326
crash while manipulating images - icm32.dll
Last modified: 2008-01-15 12:54:23 UTC
Steps to reproduce: it happens usually quickly, though "at random". An easy way to reproduce it : 1. load 2 big pictures 2. in one C-a, C-c 3. in the other : C-v (cutting and pasting one image in the other one) Stack trace: none, sorry : on win XP SP2/fully patched tell me how to get it and I'll be happy to send it !! Other information:
Created attachment 46476 [details] crash popups here is a screen shot of the crash popups I get
*** Bug 304325 has been marked as a duplicate of this bug. ***
The crash is occurring in icm32.dll, which is the Microsoft Windows module that does color management. A bit of googling suggests to me that the problem may be that your system has multiple versions of that file, and is finding a bad one when it runs GIMP. (Apparently installing Yahoo Messenger on a system upgrades this dll to a newer, but buggy, version.) You can either try to fix the problem based on this suggestion (look at http://www.p2p-zone.com/underground/showthread.php?t=21072 for more information), or if you don't see how to do it, please do a search on your system for all files named icm32.dll, and let us know the result.
First of all, thanks for your quick answer ! I followed your advice, and I searched on my local hard drives for another possibly buggy version of icm32.dll, but found just one, the one in the system32 folder. This version comes from the WinXP SP2. I then followed the advice on the link you provided, and there was a "how to delete this file" (working around Windows Protected Files) and so : * I deleted the file in dllcache folder * I renamed the icm32.dll file in system32 * then the popup "a file from the system is being modified, please insert the CD to put the original version" -> I canceled Since then, The Gimp works fine. This is definitely not a solution I am proud of, though ;) I am not even sure what is the role of this dll, but I noticed nothing bad so far. Again, thanks for all of your help ! Stephane
I doubt that the icm32.dll from SP2 is buggy - if this was the case, we would have had many more bug reports about it. If you can identify what app has modified this file, you should report this as a bug to its developers.
I agree with that, but I when I performed the "search" on my hard disks, there were just 2 hits : 1 in the system32 folder, and 1 in the ServicePackFiles folder. They were the exact same size and the same version (but I didn't do a checksum before deleting), that's why I thought the file was from the SP2. Might be wrong, though. I can still provide the file I had in system32, if anyone's interested just let me know !
Well, in any case this is something we can't fix. I'll close this bug as NOTGNOME.
*** Bug 315623 has been marked as a duplicate of this bug. ***
*** Bug 320404 has been marked as a duplicate of this bug. ***
*** Bug 355518 has been marked as a duplicate of this bug. ***
Resolving as a duplicate of bug #316645, which has the most comprehensive discussion of this matter. Short summary: Borland is to blame. *** This bug has been marked as a duplicate of 316645 ***