Tuesday, July 6, 2010

Crash in invalid Lyrics tag fixed in 1.0.06

I've been very busy these past few months, and I still am, so I don't know when I'll be able to start working on 1.1. However, crashes still get fixed for 1.0, provided that they are reported and the reporter helps me identify what's wrong.

So it's time for 2 crash fixes, based on reports from one user. One crash was caused by invalid Lyrics tags, while the other occurred sometimes when trying to use the "folder filter" in Windows (and I guess OS/2 as well.)

Another small change is in the documentation. There is now an "uninstall" section, at the end of the "download" page

Wednesday, March 17, 2010

Issue #23 finally fixed

This is an old assertion failure, reported for the first time last August. I couldn't fix this until now because I couldn't reproduce the crash. Recently somebody else mailed me a file that exhibits the same issue, which allowed me to provide a fix.

Sunday, March 7, 2010

Time for two more crash fixes

I got several reports in the mail about crashes. This release addresses two of them:

1) Crash if frames in ID3V2 have invalid size.
2) Crash if the backup directory couldn't be created.

The fixes have been in Subversion for a while, but I was hoping I could fix a few more issues before making a new release. Unfortunately I didn't get to a point where I could understand what was happening on somebody's computer or reproduce the problem on mine, so I guess more crash-fix releases will be needed.

There's another small change in the generic Linux binaries: until now they were put directly in a bz2 archive. I realized that this way the users had to set the executable bit themselves, so now I put them in a .tar first.

Friday, January 29, 2010

Fixed issue #46

Version 1.0.03 fixes the crash reported in issue 46. GEOB frames in ID3V2 could cause a crash if they contained UTF-16 strings and the user tried to go to "Tag details".

Tuesday, January 12, 2010

More crash fixes in 1.0.02

There were several crash reports that I received by mail. They are addressed in 1.0.02. The program could crash or terminate with an assertion failure in these cases:

  1. trying to repair broken ID3V2 tags that contain images

  2. changing file names manually in the file renamer, if no pattern was defined

  3. saving tag info for files that contain an ID3V2.4.0 tag (but only in some particular, rare circumstances)