"Media scan terminated unexpectedly" on overlong comments in mp3 files

[infaktum]

The problem

The scanning of new media files stops unexpectedly if an mp3 file with a very long comment (several 100 characters) is encountered. I had this problem serveral times, when I downloaded mp3 files from media servers of my radio stations.

To Reproduce

1. Edit comment tag on an mp3 file with several 100 charcters long text.
2. Transfer file to media folder
3. Run Scan new media

The Scanner protocol shows only the current file to be scanned, but no error message. The protocol then stops. If I remove the file from the server, delete the comment and add the file again, Scanning runs smoothly. This is a work-around, however it took me a long time of re-installing everything, and setting up my whole media directory. I can live with it for now, but I pity everone who encounters the same problem without knowing what to do. :)

Expected behavior

Scanning should include all new files with not problems, adding all files to the database. Long comments should simply be ignored.

System Information (please complete the following information):

I am running the Docker image of LMS (stable version of November 2025) on my Synology. I had this trouble before with older versions of LMS.

[michaelherger]

What tagging application are you using? Would you mind sharing an example file, as I don't see this problem with my test files.