-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when reading Ogg metadata #222
Comments
I was able to narrow down the issue I think, and it seems to be due to specific tracks streamed by LMS! For example:
Track attached: Desireless - Voyage, voyage.zip Playing this track immediately crashes Squeezelite. |
I could narrow it down further to the reading of the Ogg metadata. Around here: https://github.com/ralph-irving/squeezelite/blob/master/stream.c#L399 . Somehow I realized the file I attached above has completely messed up metadata, but it should not cause a crash ideally. |
I did the OggMetadata changes in squeezelite, especially to support chained streams and feedback metadata to LMS as before only real SB could. I don't have computer access for now but depending what you mean by "messed up metadata" I think that if they have a totally wrong encoding, the yes it might happen that the parser crashes. It might a debate with polarized opinions, but as somebody coding for free open source, I can't take the time and don't want to bloat code for handling all sort of improbable input-related errors. If it's human inputs, yes, but when it is a file that is supposed to be spit out by an encoder, then the encoder must be fixed. As a general opinion, I think we destroy standards and code quality when we decide to accept all and any non-compliant protocols and files. UPnP is as very good example of that. It should be a Darwinian process: your apps is not compatible, it should be selected out... |
Thanks for your reply. In this case the file is still valid and not corrupted, it's just that the metadata is weird, big and very repetitive (due to: beetbox/beets#4528 )
Metadata attached: vorbiscomment.txt So without entering the debate too much 😉 , still a valid file I think (passes |
So the weird/big/repetitive issue is caused by a beet bug (now apparently fixed)?
While I agree that a parsing crash in SL is less than optimal, seems that the right approach would be to address the weird/big/repetitive metadata issue first.
Just my opinion, not trying to wade into an argument.
BL
|
The Beet bug is fixed indeed, and I fixed the metadata in my files. So for me, it's good as it is. However I suspect it reveals a weakness in the metadata parser that might be worth looking into... |
Hi, I am experiencing crashes on Arch Linux, I think following an update of my system that replaced PulseAudio with PIpewire. Unfortunately I'm not too sure how to troubleshoot this.
For example, everything worked fine for a couple of hours then it crashed suddenly. In the system logs:
Attached dumped core:
core.squeezelite.967.745223802fc8470a98e5e231d7c14080.448.1714310452000000.zst.gz
Then after that it fails to restart:
It looks like it cannot access the audio device somehow? When I try using
aplay
I get a similar error:I'm not sure where to go from there unfortunately...
The text was updated successfully, but these errors were encountered: