That's why i keep suggesting it's probably just a corrupt/ bad index entry.
A common problem with searching exists around existence of data. It's a reasonable assumption that your database indexes are correct... if they aren't, that's a problem that needs to be fixed in your database (corollary: it's a bit of a rabbit hole to code assuming that nothing in the project is correct and functional... it can result in major inefficiencies).
Pseudocoding, the galaxy map lookup probably looks like:
- searchForFeature(name)
- if no results, do nothing
- if results:
1. Get first result
2. Play audio for result (as the audio starts before anything happens)
3. Move to result location
4. Etc
... but if we're dealing with a corrupt index, the result probably points to null data. 2. Is then trying to play audio on a feature which doesn't exist which would crash.
It'd be totally fair to code assuming the feature exists; why would it be in your index if it didn't exist, on the assumption your index is functioning correctly.... and so an audio failure would just be the first thing of potentially many that goes wrong.
Play audio could check if audio exists and fail cleanly, but if the object you're trying to call that in doesn't exist, your hot out of luck... and again, why would you not assume it exists... the search you just did said there was a system by that name... but that system is probably just on someone's dev environment.