Exceptions tracebacks are shown too late to be very useful
Created originally on Bitbucket by gward (Greg Ward)
When TortoiseHg has an unhandled exception, it's not shown until you close the current window. That has two annoying consequences:
operations that fail because of an exception fail silently, with no indication to the user that something went wrong
when the stack trace window eventually pops up, it's long after the event in question, making it hard to figure out what GUI action resulting in a stack trace
The easiest answer is just to let stack traces be written to the console. I expect that won't fly in the Windows world; it's also rather rude to a Unix user in the default "GUI fork" mode. Perhaps a command-line option to enable tracebacks to stdout? Maybe do it automatically in --nofork mode?
The fancy whiz-bang answer, of course, would be to pop up an "Internal error" dialog. Or better, put "Internal error" in the status line with something the user can click to get detailed info. After all, a stack trace is useless unless the user is going to report or fix the bug.