For me the most interesting case is HeidiSQL. I find it easily the most useful SQL GUI client, but it crashes pretty frequently, but not frequently enough for me to stop using it over the alternatives.
I often wondered how to strike the balance right on these things, since apparently all options can lead to success.
Might depend on the quality of crashes. Losing hours or days of work would quickly sour me. HP RGS crashes, twice or thrice daily are just 'meh' - reconnect and nothing - but 15 seconds and typing auth tokens - is lost - maybe 'flow' but I've become resilient there.
I often wondered how to strike the balance right on these things, since apparently all options can lead to success.