View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002398 | MMW v4 | Burning / Disc Handling | public | 2006-02-28 13:57 | 2006-03-09 00:46 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Summary | 0002398: Configuration Settings and Now Playing playlist are sometimes lost | ||||
| Description | According to users (and as experienced once by myself), MediaMonkey sometimes gets into a state where it: -doesn't save config settings (or reverts to initial settings) -doesn't save mediamonkey.m3u at shutdown -resets the database to a clean db (reported by only one user--not sure if this is real) The problem was first reported by technojnky in build 943 (beta 2). | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?t=8454 http://www.mediamonkey.com/forum/viewtopic.php?t=8459 http://www.mediamonkey.com/forum/viewtopic.php?t=8461 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 949 | ||||
|
|
Fixed in build 948. - I found a problem that could cause not-writing of MM.ini or other issues. I hope it is what users described in forum. |
|
|
Re-opening--it's still apparently an issue as described at: http://www.mediamonkey.com/forum/viewtopic.php?p=38691 |
|
|
After a fair bit of testing, it seems that this issue can be reproduced as follows: 1) Open MM 2) Load a HUGE playlist into Now Playing 3) Close MM 4) Re-open MM (there'll be a message in the status bar 'Now Playing: Reading tracks...' 5) Make a config change 6) Close MM 7) Re-open MM 8) The config change will not have been saved i.e. this problem is related to the loading of the Now Playing list. Note: this does not occur consistently with build 948. I've posted two debug logs in which this did occur. |
|
|
As requested I performed the tests described in my previous comment on Alpha 1 (build 942) and Alpha 2 (build 943). Findings are that: 1) On 15 test runs on build 942, I could not reproduce the problem 2) On 5 test runs on build 943, I was able to reproduce the problem twice This seems pretty conclusive that something introduced in build 943 is the cause. |
|
|
Fixed in build 949. - Termination issue in d_WMDM was fixed. |
|
|
Verified 949. |
