View Single Post
Old 03-08-2022, 11:06 PM   #83
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,958
Karma: 6361444
Join Date: Nov 2009
Device: many
I understand that it might be hard to reproduce, but without a bug report we would not be able to see that others were experiencing the same thing. That means whatever caused the crash is not specific to your setup. This is important.

It is very very unfortunate the Windows does not have the equivalent of the macOS built in CrashReporter that produces a report of quite useful backtraces and crash diagnostics. These can be copied after a crash and posted here (or sent automatically to Apple who would junk it since it is not their software).

That way useful debug information is available for every crash. There probably is some way to do that or some program to do that on Windows, but I have never seen or heard of it from Windows users (so if it exists it is not installed on most systems).

Either way, just the "me too" information could prove useful.

Thanks.

KevinH
KevinH is offline   Reply With Quote