View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011439 | MMW v4 | Other | public | 2013-11-01 16:34 | 2014-02-13 17:10 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | block | Reproducibility | sometimes |
| Status | resolved | Resolution | not fixable | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | ||||
| Summary | 0011439: DB Locked after initial Update | ||||
| Description | After Upgrading from 1668, on first start and DB update MMW showed number of errors. ELF is Uploaded to FTP. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | |||||
|
|
There is SQLite error "database is locked (5, 5)" in the ELF. As discussed with Peke, he run two MM instances at once (one as server and one as client) and the error was result of collision of the two MM instances writing to the same MM.DB on the same time (the one in the log was updating podcasts). |
|
|
As discussed over IM with Jiri, SQLite has never been fully ready for sharing between more MM instances. If one instance locks the DB for writing and another wants to write then this error can happen. Leaving open to see if there can be improved something |
|
|
NOTE: as pointed on IM Two instances OF MMW were started with eachother after Lunch MMW from Setup dialog. Eg. one instance was parent of second one. First one was doing DB update I guess. Check if there is possibility that elevation triggered second MMW start? |
