View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006278 | MMW v4 | Synchronization | public | 2010-02-21 18:38 | 2010-02-21 18:38 |
| Reporter | user_chrisjj | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Platform | Windows | OS | XP | OS Version | - |
| Summary | 0006278: Crash can leave corrupt file on device, maybe | ||||
| Description | I am guessing - only guessing - that an MM crash during sync can leave corrupt the currently copying file on the device yet record that copying was completed. I say this because it is the most likely explanation I see for an ongoing issue here. Ssince approx a year ago when I started using MM auto-sync to a HD folder via d_USBMass1.DLL and a SUBST drive, a period during which I have frequent MM crashes, occasionally I have found an output file to be corrupt - past some point all bytes are zero, even though name, size, and date are correct. Fair enough... except that a repeat sync does not remedy the corruption, as if MM were falsely records that the file was copied completely. It should take only a few moment for the Devs to check this is the code. It would be nice to get it fixed. Reported at http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=47018&start=0 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
