View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001593 | MMW v4 | DB/FileMonitor | public | 2004-11-11 21:41 | 2004-11-14 03:09 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | block | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 2.3 | ||||
Summary | 0001593: View corruption problems | ||||
Description | Some set of circumstances causes the situation in which for any Library node containing a specific set of tracks (i.e. the tracks in Santana's Greatest Hits album), a) selecting any track in the node causes the track to visually change (but not in the db) to the first track in the album, so that multiple instances of the track appear b) as a consequence of a) sorting in the node by anything other than Track# and then triggering a refresh, causes multiple instances of the first track to appear Note that deleting the first track in the Album causes the bug to migrate to the second track (i.e. multiple instances of the second track will appear when a) or b) is done). Note that deleting the last track in the Album (which actually results in deleting the first track because selecting the last track causes it to change) causes the bug to migrate to the third track (i.e. multiple instances of the second track will appear when a) or b) is done). Circumstances which trigger the bug: The only known way to consistently trigger this set of circumstances is to rip the Santana CD (or load a database into which the CD was just ripped). Circumstances which stop the bug: Once the bug is occuring, it can be completely stopped by: -Deleting the complete set of tracks involved in the bug from the database and rescanning them -Rescanning the complete set of tracks involved in the bug without removing them from the db Circumstances which fail to trigger the bug: -Scanning the tracks that have been ripped In all cases, though, an examination of the filesystem reveals that the files were all ripped correctly--i.e. it's either a database or display problem. ---------------- A second, related issue is that upon attempting to delete all ten tracks from any library node in which those are the only tracks that exist, the tracks all disappear, but upon refreshing the node, some tracks come back!! (and I can confirm that they weren't deleted by looking on the HD)! I've replicated this behaviour for both OGG and MP3 rips, on both WinXP and Win2k (on 2 different computers one very fast, the other slow). File Monitor was disabled in all tests. Most significantly, I'm only able to replicate this with this particular Santana album!! | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||