View Single Post
Old 11-14-2019, 10:14 AM   #108
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
Quote:
Originally Posted by [KevinH View Post
Unfortunately, I do not think Windows makes it easy to get a core dump.
Yay Windows .

Quote:
Yes, Doitsu reported the same warning message.
Ahh, I missed that. So Linux and Windows have the same warning.

Quote:
Originally Posted by Doitsu View Post
I haven't been able to reproduce this bug on my Windows 10 (1909) machine with 0.9.991-21.

I've opened and closed all 50 images twice by pressing CTRL+W and didn't get a crash. Have you installed the Windows 10 1909 update?
One more thought. Did you press and hold down ctrl-W so that it auto-repeated, or did you bang on lots of individual ctrl-W's? This seems to be somewhat timing related. I wasn't able to reproduce problem with fast individual ctrl-W's. I needed the auto-repeat speed to have a chance of reproducing the fault.
snarkophilus is offline   Reply With Quote