View Single Post
Old 05-08-2018, 04:50 PM   #409
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,918
Karma: 6240958
Join Date: Nov 2009
Device: many
Yes, the cancel button sends a kill signal to the forked process, which then terminates resulting in the Launcher process crashed message.

Since no result xml was written then we get the last Error Parsing message. I could change it so that when a Launcher Process crashes (or is killed) that the result xml is simply never read to prevent the last error message if that is causing some problem for Windows.
KevinH is online now   Reply With Quote