View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005112 | MMW v4 | Synchronization | public | 2008-12-31 00:35 | 2009-01-05 20:17 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Summary | 0005112: Multiple Auto-Convert Operations can Trigger out of space Dialog | ||||
| Description | As Reported by user, if MediaMonkey has a large auto-sync operation in which it auto-converts a large number of tracks, all of the tracks are auto-converted at once, which can cause e.g. 30GB to be filled with temporary files and an out of space error. It would make sense to optimize/avoid this by auto-converting a large batch of files in numerous smaller batches. Example: Synchronizing music tracks is a two-step process under these conditions: Step 1 - MediaMonkey writes a temporary file (leveled and/or converted) for each track to the temporary directory. Step 2 - MediaMonkey transfers the temporary file to the Zen. On some set-ups, step 1 occurs faster than step 2. Which can result that during the course of syncing 4,600 music tracks, the number of files on the temporary drive builds up. At some point during the progress of the syncing (about half of the music tracks had been processed by MediaMonkey) the temporary directory contained approximately 1,400 files taking up about 5.5 GB of space. In case that Temp gets out of space Dialog is shown. It seems logical that if MediaMonkey runs out of space in the temporary directory, it should stop (or slow down) step 1 until step 2 catches up and more space becomes available in the temporary directory. | ||||
| Additional Information | Ticket: NNY-470475 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
