View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017891 | MMW 5 | Casting (Google Cast / UPnP) | public | 2021-05-20 01:20 | 2021-06-20 12:51 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0.1 | ||||
| Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
| Summary | 0017891: Background processes / Crash on startup (ID 0AF359A7) | ||||
| Description | While testing slow closing time while visiting web nodes, I noticed that MM would sometimes start displaying SASstream messages in the logs, and that terminating MM while those messages were appearing resulted in a 'This will terminate background processes' message. afaik, nothing was connected to MM, but MM indicates that the Chromecast home group was last active, though I can't imagine why. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2406 | ||||
|
|
The crash 0AF359A7 was only successor of 539F6172 that you submitted. The 539F6172 shown the real reason for the crash (was a timing issue realted to UPnP init) => Fixed in 2406 SAStream appears only during playback AFAIK (or volume analyzis while decoding) -- and there isn't any SAStream in the 'crash-on-startup_associated-with-crashlog-id-0AF359A.LOG' Re: 'threads running on close.LOG' -- based on the log MM5 was analyzing volume on background, so the progress was probably missing --> already fixed by Michal as 0017875 for 2406 |
|
|
Verified 2418 Unable to crash or replicate. NOTE: I especially watched for cases explained in 0017891:0063323 |
