Hi, On Fri, 2009-12-18 at 14:33 -0500, Jay Smith wrote:
> If I were a developer, with the necessary skills, I would be curious > about what was killing off the plugin and why the plugin dieing > (especially when it was just trying to open a dialog and had not > actually attempted to take action on the image yet) would leave the > whole program in a potentially unstable state. The message that tells you about the dying plug-in is just a general dialog. It says that GIMP 'might' have been left in an unstable state. In general this is not the case and there's nothing to worry about here. I have written the plug-in that crashed, and I can tell what's most likely going wrong, without having a look at the code or your broken image. The assumption that the plug-in would not have accessed the image before it opens the dialog is wrong, since the plug-in needs to read the color profile from the image in order to present information about the current color profile to the user. If the attached profile is corrupt, then it may crash at this point. I don't really care about fixing this for all sorts of corrupt input data. Such a fix would most likely introduce regressions and would make the code much more difficult to read and maintain. You can probably get the plug-in to do its job of removing the attached color profile by calling the plug-in procedure non-interactively. Or you could simply remove the "icc-profile" parasite from the image. Sven _______________________________________________ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
