Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-2520

Null bytes in tag values can cause crashes when sorting

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 2.8.4
    • 2.8.2
    • Lookup & Match
    • None
    • Win10 x64
      Ryzen 5800x on x570 chipset
      Media on mapped drive within intranet

      Had an occasion where Picard repeatedly crashed on a Lookup for a particular album of FLAC files.  This is the only album of 20 or so that has crashed so far with this Picard version. 

      The filenames were normal characters and the path length was typical.  This same album could cluster okay, and it also scanned okay as well - with a caveat: one scan failed (crashed as above) while I was troubleshooting, but that was it.  In the end, I was able to complete tagging for this album after a successful scan.

      To doc the crash, I started Picard in debug mode within an admin command window.  I loaded the album, allowed it to cluster, then selected Lookup.  The app crashed as expected.  I copied the text from the command window and have attached it.

      My plugins are:  Additional Artist Variables, Feat. Artists in Titles, Load As Non-album Track, Padded disc and tracknumbers, and Replace forbidden symbols.

      I'm assuming scripts haven't been called yet before the crash, but if you'd like those or anything else, plz let me know.

        1. Picard Debug log.txt
          71 kB
        2. Picard Debug log2.txt
          103 kB
        3. Picard_User_Backup_20220713_0637.ini
          33 kB
        4. Win App Error.txt
          2 kB
        5. track compare.rar
          6.60 MB

            outsidecontext Philipp Wolfer
            ecomaniac ecomaniac
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:

                Version Package
                2.8.4