View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016434 | MMW v4 | Synchronization | public | 2020-03-12 20:30 | 2020-03-16 21:50 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1.27 | ||||
| Target Version | 4.1.28 | Fixed in Version | 5.0.0 | ||
| Summary | 0016434: Sync: MM4 freeze on device connection | ||||
| Description | MM freeze on device connection, device profile creation and initial device content scanning. Logs and portable folder sent to Ludek offline. | ||||
| Steps To Reproduce | 1. Install 1897 Portable to c:\MMTEMP (Cancel launch on installation end) 2. Start MM4 -> Cancel all first start wizards as Library and settings are not important) 3. Connect Device 4. Device profile is created Config dialog is shown -> Cancel 5. Device in tree shows Scanning 6. Click on Now Playing in tree 7. MM freeze and crash after timeout 8. Disconnect phone 9. MM4 is accessible and working again. 10. Close MM 11. Try to delete c:\MMTEMP -> Fail Admin access needed 12. Enter c:\MMTEMP and delete all files and subfolders -> ALL OK 13. Delete c:\MMTEMP -> ALl OK | ||||
| Additional Information | GCB-879-52664 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This is a very strange bug, which I never encountered before, especially as MM4 works perfectly until you connect Device. User Have MalwareBytes Anti-Virus. We will test behavior on MM5 portable to compare and see if problem is with MM or with user specific settings in order to see what can be done. |
|
|
I cannot replicate the issue using content of Portable folder from the "Mm Clean Portable.rar" archive that you sent me offline. I also don't understand step 4. Device profile is created Config dialog is shown -> Cancel as I am not aware of any automatic pop-up of a config dialog (user needs to click the device node in MM4 media tree to see the embedded config -- i.e. not a dialog with cancel button) ? From the "crashlog.elf.txt" that you sent me I see that UI thread has frozen when getting view data from database. This cannot happen in MM5 as in MM5: 1) _all_ database access is from non-UI threads (asynchronously) 2) view data are no longer stored in DB, but in persistent.json So I would consider this issue as resolved in 5.0.0 ? |
|
|
We tried few more things and phone settings, but phone crashed and user sent it to repair. It was factory reset and apron returning today all worked and MMA reinstalled and synced. |
