I think this should be closed. If it can be reproduced on a modern version of beets with more details then that can be a new bug report, but in any case it's probably better off being reported upstream.
This bug is pretty much impossible to investigate without having more
information, such as the actual files that exhibit the issue, verbose
output from beets, the output of `beet info` for the relevant files, etc..
