Make KLAS Die Quicker

This may sound like a weird question, but have developers investigated way to make KLAS die quicker? When KLAS crashes, I just want to see its tombstone (you know, its error report). Then, when I click OK on the error report window, that's it. KLAS has closed and no services remain running in Task Manager. I don't like the Rasputin death of infinite loops of Whac-A-Mole. Admittedly, I go to Ctrl+Alt+Del pretty quickly, but I'm curious if there have been any recent discussions for KLAS to die quicker and more mercifully. Is a better "death" on the horizon? Could it be a KLAS 8 thing?

-Dan

This is theoretically possible. It would involve tracking down the problems that cause it, and identifying the error(s) to make "fatal," which will stop the cascade and just close everything.

It does come with the risk of sometimes closing everything when the error would otherwise have been recoverable.

If this is something people want us to prioritize, let us know and I'll report to Development and KDAC accordingly!

Thanks for the follow-up, Katy.

Needless to say, I vote for an immediate Thanos Snap terminating KLAS with just a little cryptic note saying why it has stopped. In all my years of using KLAS, my confidence that KLAS will recover once error messages persist is very low. I feel more certain when I login anew so I'd prefer to get to that step quicker.

That said, I worry that benign error messages - like the ones I get because I have modified my font types and sizes in the user.ini file - could trigger a Thanos snap making it impossible for me to ever open certain windows/functions. I'm not sure if that fear is reasonable. (I won't be present for the next KDAC; maybe we can wait until October to discuss?)

-Dan