On Mon, Jun 04, 2001 at 09:46:12AM +1000, Ben Stanley wrote:
> The main reason I was concerned about this is that the message you get from
> gimp after xsane crashes (or is killed) suggests that gimp's internal memory
> structures may have been corrupted, and that you should re-start gimp. That's
> all I have to go on.
We can't detect whether the plug-in went crazy before it died, and so
we just advise users to restart if a plug-in suddenly crashes. This is
a general warning on a "better safe than sorry" basis.
Actually 99% of crashes are completely benign, and don't adversely
affect Gimp at all. This is very helpful when testing a plug-in because
you don't need to keep re-starting Gimp :)
For your case, where we know that everything the plug-in did before its
death was sane (pardon the pun) you can continue without significant
additional risk of data corruption or problems AFAIK.
Nick.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sun Jun 03 2001 - 20:27:13 PDT