As a programmer, I would have included a fail safe timer in the camera OS.... So many seconds have gone by without a refresh, force a reset.....
Canon is not responsible for Kenko's problems, but their camera should not lock up under an error condition, it should at least display an error code.....
Bad code is bad code. If your code doesn't do proper error handling, your code is s**t, period. It doesn't matter what triggered that code to crash. It's still a security hole waiting to happen. And as I said, bad code in one part almost invariably means that you have bad code throughout. These sorts of problems lead me to the inevitable conclusion that their entire firmware is probably held together by shoestrings and bailing wire. That's not very reassuring, speaking as someone with $15k invested in Canon gear.
The part that's more infuriating is realizing that a one-line bug fix would probably make these things work, if we could just get the bug report past the CSRs to the engineering team.
Perhaps. Improper error handling should not happen in a perfect world. However, I hope you will concede that Canon can only test and recreate error conditions it has control over. That's the case for any software development process. We have no idea what Kenko is doing in their reverse engineering efforts that causes a camera to lock up, and that's really my point - neither does Canon.
I am not going to question my $35k+ (and counting)
in invested Canon gear when an unlicensed, third-party, reverse-engineered teleconverter locks up my camera. I'll just take out the battery, reinsert it, and then think twice about buying non-Canon gear in the future.