I'm not able to replicate this with MMW 139 against MMW 1642 (expected to be posted shortly) on an S3.
Is it a display bug (i.e. only visible when the tracks on the device are viewed from within MMW), or a sync bug (i.e. the tracks have these errors when viewed on the device as well)?
My guess is that it's a sync bug, so I'd ask you to delete the tracks and resync with the latest MMA/MMW builds and see if you can replicate (there are many sync fixes in recent builds).