FYI in case anyone's interested, the Open Source library that they're using to replace IE can be found here:

https://github.com/cefsharp/CefSharp

184 contributing developers is high. In other words, stability can generally be expected to be good with this one. That said, a glaring design oversight shows up in the CefSharp stack trace provided by @yfegade in the original report.

No app/library that allows unhandled exceptions to occur should be released into production. Doing so represents just about the worst of the worst in poor programming practices. An unhandled exception is one that bubbles up to the top (the code's entry point) and isn't caught by what's called a Global Exception Handler. The irony of it is that such a handler is quite easy to implement in code.

There exist techniques a developer can employ to mitigate this problem, should it be found to be present in a given third-party library (which this is, from Intuit's perspective). Let us hope that they decide to make good use of the stack trace that @yfegade has provided and quickly get to the root of the problem.

I'm not holding out much hope, however. I'm not at all impressed with what I've seen coming from the desks of Intuit developers. The absolutely childish, immature and horrid UI/UX provided by their oft-touted ToolHub is just one of many examples. Intuit actually brags about that? Incredible. They must not be paying enough to attract a crew that knows what it's doing.

Intuit's executives are fixed at the helm of an abusive monopoly.