View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017661 | MMW 5 | Playback | public | 2021-03-12 02:12 | 2021-03-18 00:04 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0017661: Clicking NEXT to play through numerous tracks --> failed playback error OR crash C000005 | ||||
| Description | 1 Launch MM in Locations > path [Browser:recursive mode] 2 Double-click first track and click NEXT through several tracks to verify that they're local (i.e. listen to each for a fraction of a second) --> after about 6 tracks: crash C00005 Tested in build 2323, however this doesn't appear to be a recent regression. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2326 | ||||
|
|
I also just noticed that clicking the NEXT button _really_ quickly to advance through multiple tracks often results in a toast message for some of the tracks that "Playback failed. <path> cannot be decoded." even though these files play normally. Also, I noticed that Memory utilization steadily increases when doing this. Lastly, re. crash C0000005, I've discovered that it can be relatively easily replicated by continually clicking NEXT or PREVIOUS to switch tracks even after the Playback failed error has occurred. NOTE: I don't have the codec pack installed. |
|
|
Fixed in build 2326. I have fixed wrong "...cannot be decoded" error and cannot reproduce the crash any more. |
|
|
Verified 2326 Key test note was that playback must start before next is clicked. |
