GNOME Bugzilla – Bug 314529
Certain versions of GTK+ shipped by Gaim can crash GIMP (e.g. Crash on stroke fill)
Last modified: 2008-02-02 19:55:10 UTC
Steps to reproduce: 1. Highlight text 2. Go to Edit 3. Click Stroke Selection, then OK Stack trace: Other information: Everytime I try to fill a stroke on text, GIMP crashes. I am using Windows, so I cannot provide a stack trace.
Of course you can provice a stack trace. But you will need to compile a version of GIMP with debugging info and you will need a debugger. But since this problem seems to only show up on Windows, it is unlikely that we will be able to fix it unless someone obtains a stack trace on Windows.
This might help to locate the problem. Valgrind reports the use of an uninitialized variable: ==3592== Use of uninitialised value of size 4 ==3592== at 0x81C11E0: gimp_drawable_stroke_boundary (gimpdrawable-stroke.c:129) ==3592== by 0x81A6876: gimp_channel_stroke (gimpchannel.c:741) ==3592== by 0x820014F: gimp_selection_stroke (gimpselection.c:307) ==3592== by 0x81EE6AE: gimp_item_stroke (gimpitem.c:1002) ==3592== by 0x809625B: stroke_dialog_response (stroke-dialog.c:296)
*** Bug 310186 has been marked as a duplicate of this bug. ***
If you could link to a decent compiler for Windows for GIMP, and link to/explain how to debug it etc, I'd be happy to provide a stack trace. I'm not too experienced with debugging on Windows, only *nix.
Jack, there is nothing more you need to do at this point. The information in comment #2 should be enough to make the problem solvable. I am going to confirm this bug report accordingly.
I don't think we have enough information to solve the problem. It is for example still unclear whether the crash happens when stroking using a paint tool or only when using libart. Also, since it isn't reproducable on Linux and not even the use of the uninitialized variable reported by valgrind is reliably reproducible, I don't see how we could debug this problem without the help of someone running GIMP on Windows.
I have found that this bug also occurs when you do any of the following: - Create some text, click the "Create path from text" button, click Select->From Path, and then click Edit->Stroke Selection... - Create some text, click "Create path from text" button, click Edit->Stroke Path... - Create a selection with the rectangle selection tool and click Edit->Stroke Selection... - Create a selection with the rectangle selection tool, click Select->To Path, click Edit->Stroke Path... I hope this helps.
I forgot to mention that it doesn't matter if you use the "Stroke line" or the "Stroke with a paint tool" option in the "Stroke Selection/Path" dialog. I also just discovered that when you click "Cancel" in the "Stroke Selection/Path" dialog the gimp crashes.
I just uninstalled Gtk+ 2.6.9-rev A and installed the Gtk+ from gimp-win's web page (2.6.9) and all is working fine. It must be something with 2.6.9 rev A.
That is also what some of the comments in bug #310186 indicate.
I had the same problem. Upgrading GTK+ from 2.6.8 to 2.6.9 (along with upgrading GIMP from 2.2.7 to 2.2.8, but that doesn't seem relevant) solved it.
*** This bug has been marked as a duplicate of 310186 ***
Circular duplicates aren't cool; please pick a different resolution.
Drawing the most simple strokes on Windows simply crashes (image not saved, the program exits immediately) immediately as soon as one click on the "Draw path" button. It's IMPOSSIBLE to draw segments in Windows. Also there should exist a way to edit paths so that points will not be absolute angular but rounded, and direction control points can be also added (I mean quadratic or Bezier curves). Please also add exception handlers around GIMP extensions, so that they won't crash immediately and will give the opportunity to save the current work, possibly in a backup file, that can be restored nearly automatically from the "recent images" list, when The GIMP is restarted and an image is selected that has a backup version in the same folder.
Re comment #14: please don't mix entirely unrelated issues in one bug report.
Comment #9 and comment #11 seem to indicate that the resolution is either NOTGNOME (because it happens with only one binary build) or FIXED (2.6.8 -> 2.6.8 fixed it).
Note that the bug report #310186 (which is marked as a duplicate of this one) explains how to resolve this problem.
*** Bug 318145 has been marked as a duplicate of this bug. ***
So this is yet again an incompatiblity with the GTK+ shipped by GAIM? Don't they use the binaries from gtk.org for their installers?
I believe I finally understand the cause of this crash. Here's the situation. Gaim, a popular open source chat client currently requires Gtk+ for it's operation on Windows. Gaim is at version 1.5.0 right now, and they have all resources set on Gaim 2.0, so nothing is being done with version 1.5.0 . Gaim for Windows version 1.5.0 includes Gtk+ 2.6.9a . Gtk+ 2.6.9a has the crash on 'stroke', while Gtk+ 2.6.9 does not. Many of us download Gaim 1.5.0 first, and then properly only install Gimp 2.2.9 because we already have the Gtk+ 2.6.9 . However, we actually have Gtk+ 2.6.9a which has a crashing bug via applying stroke to letters or the pen tool. Solving this problem: 1. Politely request Gaim 1.5.0 to be packaged with Gtk+ 2.6.9 to avoid later unneeded bug reports due to outdated Gtk+ 2.6.9a bugs. 2. Go to Start>Settings>Control Panel>Add/Remove Programs 3. Select Gtk+ 2.6.9 remove only 4. Once finished, download 2.6.9 from http://gimp-win.sourceforge.net/stable.html 5. Extract to Desktop via WinZip 6. Run installation program 7. Select yes, use the same folder that still exists 8. You should have a proper working Gimp 2.2.9 I do hope this helps everyone. It seemed like a wierd problem, with first people saying they were having problems with their Duron, but not their Pentium. Then someone else would say they were having problems with their Pentium III. And the number of duplicate reports abounds. However, I believe this is the problem, and this is the correct fix. Good luck with Gimp, everyone.
I quote a new message in entirety: >Comment By: Daniel Atallah (datallah) Gimp's package isn't "fixed", it just uses an older version of the gtk-wimp configuration that has a setting disabled which happens to prevent the crash. The gtk+ 2.6.10a package available from the gaim sf.net downloads page which actually contains a fix to the problem. After looking at the downloads page, I did not find the 2.6.10reva, so I clicked on another link on the page, and found it on > http://sourceforge.net/project/showfiles.php?group_id=235 < So, the response is to recommend using gtk+2.6.10a found at the link above, instead of gtk+2.6.9 at > http://gimp-win.sourceforge.net/stable.html < I'm going to uninstall gtk+2.6.9 from the above link, and going to install gtk+2.6.10a and see what happens. Good luck to you all...
After using gtk+2.6.10a, I've found that there is no crash on applying stroke. However, there does seem to be a crash on using the zoom option built into the picture window. I have not checked if the zoom through the navigation window works yet... so far, in what little testing I've done... gtk+2.6.10a seems workable with kinks.
I have not been able to repeat the crash I noted before... 2.6.10reva appears solid.
Do they use the binaries from gtk.org now?
*** Bug 321580 has been marked as a duplicate of this bug. ***
*** Bug 323769 has been marked as a duplicate of this bug. ***
*** Bug 323018 has been marked as a duplicate of this bug. ***
I'm changing the summary to indicate that the problem is rooted in some version of Gaim's gtk+. Could someone who's using Gaim open a bug report there and refer to this bug? And please tell them to use the official gtk+ binaries available from gtk.org, if they don't do this already. I'm unsure whether to leave this report open or not, but let's at least reopen it.
*** Bug 324324 has been marked as a duplicate of this bug. ***
*** Bug 324755 has been marked as a duplicate of this bug. ***
I have now filed this with the Gaim bug reporting system: http://sourceforge.net/tracker/index.php?func=detail&aid=1389095&group_id=235&atid=100235 Those interested could go add themselves to the watch list to see what falls out.
*** Bug 324372 has been marked as a duplicate of this bug. ***
The GTK+ installer that gaim provides does use the "official" binaries that Tor creates.
*** Bug 325852 has been marked as a duplicate of this bug. ***
*** Bug 320999 has been marked as a duplicate of this bug. ***
(In reply to comment #33) > The GTK+ installer that gaim provides does use the "official" binaries that Tor > creates. That's great news. Comment #22 apparently indicates that there is a 2.6.10 installer available from the Gaim site that doesn't cause the problem this report is about. However, http://gaim.sourceforge.net/win32/index.php#wingtk links to 2.6.9, which presumably still triggers it? I thought about adding a news item to gimp.org in order to get more attention to this problem (and have less duplicated bug reports), but I'd prefer if you could notify your users on your own - I don't like to cause something that might look like we're bashing Gaim.
(In reply to comment #36) > However, http://gaim.sourceforge.net/win32/index.php#wingtk > links to 2.6.9, which presumably still triggers it? I updated that link to point to 2.6.10. The gaim 1.5.0 installer that is packaged with GTK+ (we provide installers with and without GTK+), however, still installs 2.6.9 (I didn't want to re-release and deal with complications associated with that.). Thanks.
If users ue this GTK+ installer, will their 1.5.0 installation be updated? If so, it would IMO be best to announce this in your news system.
*** Bug 330077 has been marked as a duplicate of this bug. ***
I've opened bug http://sourceforge.net/tracker/index.php?func=detail&aid=1425996&group_id=235&atid=100235 in the Gaim bug tracker to make the Gaim developers aware of this problem. If nothing happens this week, I'll add a news entry as mentioned in comment #36.
*** Bug 320670 has been marked as a duplicate of this bug. ***
*** Bug 333775 has been marked as a duplicate of this bug. ***
*** Bug 342324 has been marked as a duplicate of this bug. ***
*** Bug 344465 has been marked as a duplicate of this bug. ***
*** Bug 345529 has been marked as a duplicate of this bug. ***
*** Bug 334351 has been marked as a duplicate of this bug. ***
*** Bug 334182 has been marked as a duplicate of this bug. ***
Lowering priority because there is nothing we can do about this.
My W98SE with Gimp 2.2.10 would crash when I did File/New/OK. I believe this is related to the above problem. I just upgraded to Gimp 2.2.12, it still crashed, with Windows reporting ...illegal operation and will be closed down. I have C++ installed, and debug reported... debug: unhandled exception in gimp-2.2.exe (LIBGTK-WIN32-2.0-0.DLL): 0xC0000005: Access Violation. I thought I had SourceForge's GTK 2.6.10 installed, but when I installed gtk-runtime-2.6.10-rev-a.exe, it reported I was running 2.6.9 rev A. I had to reboot to get it to install completely (I hadn't after crashing Gimp). Gimp now will open a new file for me. It does seem to be a GTK problem. Good luck to all of us W98SE users (mine is internetting from behind a Devil Linux CD-boot firewall machine). My thanks to all who report problems and solutions online.
*** Bug 348609 has been marked as a duplicate of this bug. ***
*** Bug 350750 has been marked as a duplicate of this bug. ***
*** Bug 390397 has been marked as a duplicate of this bug. ***
*** Bug 381107 has been marked as a duplicate of this bug. ***
*** Bug 408266 has been marked as a duplicate of this bug. ***
*** Bug 410574 has been marked as a duplicate of this bug. ***
*** Bug 437577 has been marked as a duplicate of this bug. ***
This could probably be marked as a duplicate of gtk bug #311141. Upgrading to gtk+-2.8 or later would solve the problem. The backport mentioned in that bug report came after 2.6.10 and was never included in a 2.6 release, so 2.8 is required.
Sorry, ignore my previous comment. The gtk bug mentioned above is not related to the same thing as this bug report, even if upgrading would also solve that problem.
*** Bug 458462 has been marked as a duplicate of this bug. ***
Note that to correct the aforementioned bug 458462 I installed GTK+ 2.10.13 which fixed my Gimp 2.2.17 crashes but broke my Gaim 1.5.0. Given the comments about Gaim in this bug (314529), I thought I'd mention that Gaim has been superseded by Pidgin 2.0.2 (http://pidgin.im/pidgin/home/). I mention this because Pidgin 2 wants to install GTK+ 2.10.11s...
Pidgin hasn't had a release since GTK 2.10.13. I'm not sure about Gaim, as I have upgraded to Pidgin, but Pidgin does not crash with GTK 2.10.13
*** Bug 478605 has been marked as a duplicate of this bug. ***
I guess this can be resolved as OBSOLETE, as GIMP 2.4 installers install a private copy of GTK+.