Comment 2 for bug 1467002

Is there anything to be done here? I think if we detect corruption while loading it (bad headers, etc.) then we already bail on loading it w/ a warning. In Bug #1793387 we're actually making MP3 decoding more likely to bail on the fly by stopping decoding the moment we detect something bad.

What else can we do? If we detect corruption ever, we can set a flag in the library to warn users about future uses?