Program Crashes

"Rather than crashing, it would be nice if the program notified the user what the issue is and in which measure it happened without crashing."
I think it's a bit unfair to blame MuseScore for mistakes made by optical music recognition (OMR). I use OMR a lot in order to save time, and the OMR program which I use highlights all errors where the beats in a measure don't add up correctly. So before I export the MusicXML file from the OMR software, I always correct the errors or simply delete the contents of the faulty measure.

And in fact, MuseScore already does its best to report XML import errors by measure and stave when importing a score in that format. Tip: you won't see these messages if you click the Ignore button! If MuseScore crashed, the error must be serious...

[EDIT] ... and it would be really helpful if you can upload here the MusicXML file which crashes MuseScore. I do agree that would be good to trap this error and report it rather than crashing.

Generally speaking, MuseScore does report errors rather than crash. Any error that we thought even remotely likely to be encountered, we detect and report. But every once in a while, an input file does something so crazy and unexpected, no one thought to add in a check for it, and occasionally in those cases a crash happens. When someone gives us a file that allows us to reproduce that problem, we're almost always fix the crash for the next update. And, we can also probably tell you where the error is, so you can be on your way meanwhile :-)