Quote:
Originally Posted by snarkophilus
@kevinh Using text build 376 on Win 10 build 19043.1415, open a not small epub and - type ctrl-f
- type <p
- hold down ctrl-g until Sigl crashes (approx 5-10 secoonds)
I have seen Sigil quit before once or twice before (many months ago) when doing some quick repeated ctrl-g but haven't been able to reproduce this. Seems like a simple search and press-and-hold ctrl-g is enough. When run from a cygwin command line which I've been able to capture some Sigil messages before, there are no diagnostic messages; the Sigil process just exits. If there's any debug options I can enable, let me know.
Not sure I'd consider this a show-stopper for the next release, but a) would be nice to fix now that I can reproduce, and b) you're having so much fun in the S&R code now. |
This sounds like it could be the same issue I’ve had with Sigil for a long time. I’ll be in the middle of some heavy duty editing - usually replace/find next - and Sigil will shut down. I always thought it was caused by my machine starting a new process when an old one hadn’t finished.