Originally Posted by kiwidude
@DiapDealer - no-one has reported any errors from when they close Sigil, so that is a new one to me. The Open With issue was that launching Sigil showed an error dialog box where it complained about conflicting C runtime dlls before starting up anyway. It wasn't a crash like you mention above, and the new Open With plugin should avoid that issue.
Please do keep experimenting to see if you can replicate that close Sigil crash, I have never seen that one but would like to eliminate it.
Will do. I'd like to say that when
it happens ... it happens when there's unsaved changes being discarded, but it's not every time
unsaved changes are being discarded. Perhaps a certain feature in combination with unsaved changes being discarded? I'll keep trying. I guess it could also just be my comp (although that sort of thing is definitely
out of the ordinary for my machine).
Edit: Did you get the closing crashes with the 0.5.905 build too, or just this one? That would help us track it down. As meme reminded me that sounds like a memory cleanup issue. It most likely will be that using some particular feature of Sigil is triggering it. If you can remember which feature(s) you were using in those sessions where it crashed that may help...
I never got a chance to give 0.5.905 a workout on Windows. Just Linux (and then only very casually).