On average, three quarters of a software program is already expected to making that application 'foolproof'. You can do only so much, and a 100% bugfree application will never happen. Kodi uses a 3rd party tool ffmpeg for decoding videos. Team Kodi didn't create it, but we use it because it helps us play Kodi on just about every electronic gadget there is. There isn't much else to choose AFAIK.
Dear Klojum
Thank you for this comment. Now let me try to talk seriousely.
First of all, let's split in the context of the conversation between:
1. dealing with content bugs
2. errors in the sw code itself
Now, lets talk about it.
1. Dealing with content bugs.
Yes, the majority of the code of any program is dealing with exceptions. That's why when you mentioned that "KODI follows the books" I was not impressed. The reliable software has to overcome issues. Let me give you an example. Once I was in the car navigation cartography. And we were testing a new system from BMW/Siemens. At one crossing (where it was supposed just to drive straight) it kept on telling "please turn left and then turn right". It was really a puzzle. The crossing was just a cross! We struggled for several days until our chief engineer decided to zoom to the level of 1:1, literally. ANd then he saw that the cross was not a cross: two roads were connected like the Z letter, and its size was less than 1mm in real life! So small!!! But of course for this system it was a "turn left and then (1mm later) turn right", as it followed the books.
We tested it on all other navi systems and they did not even notice it. Not because they were stupid, but because they were on the market for many years and they were smart.
Sorry, currupted files happen. Not only because of Russians, but also – as we found with you – because of HDD (although I never have seen it myself).
You have to cope with it. You have to mature the system. It's not the question of punishing those who happen to get some russian-made video, its just the question when you do it.
2. Errors in KODI itself
In my case the Raspberry crashes on this corrupted file and the OS reboots.
Whatever happens with the tool you use, It's YOUR OS which crashes.
Sorry, this is your bug, which you have to repair.
I hope I explained my two points. But if not, I am here to comment further.