View Single Post
Old 03-08-2022, 09:06 AM   #66
snarkophilus
Wannabe Connoisseur
snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.snarkophilus ought to be getting tired of karma fortunes by now.
 
Posts: 426
Karma: 2516674
Join Date: Apr 2011
Location: Geelong, Australia
Device: Kobo Libra 2, Kobo Aura 2, Sony PRS-T1, Sony PRS-350, Palm TX
@kevinh Using text build 376 on Win 10 build 19043.1415, open a not small epub and
  1. type ctrl-f
  2. type <p
  3. 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.
snarkophilus is offline   Reply With Quote