View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014801 | MMW 5 | FileMonitor / Find Missing | public | 2018-05-02 19:12 | 2018-05-02 23:33 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0014801: Crash on initial run following DB import (was Crash during scans) | ||||
| Description | Occasionally, scanning triggers a crash (it's not consistent). In this case I triggered the issue as follows: 1 Initiate scan of Temp/DL directory 2 While scan is underway press insert to initiate another scan 3 Scan froze/UI freezes at track: OH Yeah - December is grey.m4a OR OH Yeah - Ferriss Bueller.m4a Debug log: 852CE618 Update: this issue can be triggered in Petr's build 2102 (custom) even when skipping step 2 (i.e. this build contains code that wasn't included in 2102. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2103 | ||||
|
|
Further testing indicates that this bug may not even be a scanning issue, but rather related to thumbnail generation. The reason I say this is that I was able to replicate the build as follows: 1) Run clean build of MM 2) Allow it to import the MM4 DB 3) After that's complete, but while the 'hourglass' is displayed, press INSERT --> MM immediately freezes! i.e. it occurs even when scanning isn't in progress -- presumably the hourglass was displayed due to thumbnails being generated, and pressing INSERT somehow triggered the crash. Debug log: 320DB9F0 |
|
|
Further testing shows that the bug occurs even without performing step 3! 1) Run clean build of MM 2) Allow it to import the MM4 DB --> Hourglass displays and MM freezes! Debug log: 320DD6C8 My guess is that it could be related to podcast updates or thumbnail generation. |
|
|
fyi, I can also replicate this on a clean install of build 2102 (normal build) following the steps of 0014801:0050169 Debug log: 320DD6C8 Edit: I've generated another Debug log of this along with a dbgview log (attached below): 320D823D |
|
|
Fixed |
|
|
Verified 2103. |
