View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017945 | MMW 5 | Casting (Google Cast / UPnP) | public | 2021-05-29 02:05 | 2023-03-03 16:09 |
Reporter | peke | Assigned To | |||
Priority | immediate | Severity | crash | Reproducibility | always |
Status | closed | Resolution | reopened | ||
Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
Summary | 0017945: Crash on trying to select DLNA renderer and crashes on close | ||||
Description | Crash on trying to select DLNA renderer and MM5 crashes on Close. NOTE other Rendered name is containing e8200 as seen in Video Log ID attached Clean MM5 install. | ||||
Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=482295#p482295 | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 2411 | ||||
|
I think that the reason for the issue is the "Invalid class typecast" dialog seen at 0:12 on your video, but on the video there has been no [Send log] button so I can't see where this exceptions occured. Was the test on the video performed with debug build? Could you attach debug log generated usiing DbgView started prior to MM start? I suppose that specific cast device on your network is somehow causing this exception. EDIT: In the crash 91942329 on close there is part of the debug log (but it is on closing and is just consequence of the "Invalid class typecast" error shown at 0:12 of the video) --> that I need to see in the DbgView (where I could see also the list of the cast devices on the network). So please generate debug log. |
|
Another user reported same behavior, description updated. |
|
Crash 91942329 already fixed in build 2411. It happened when mediamonkey.m3u8 was missing during app start. I think "Invalid class typecast" is different error. |
|
Yes, the "Invalid class typecast" is a different error, user is not willing to debug this further: https://www.mediamonkey.com/forum/viewtopic.php?f=21&t=99144&start=15 I've done some code review and made some changes that should prevent this + added more debug strings for sure Fixed in 2411 |
|
Verified 2411 It doesn't happen with me or the user that initially had the problem when this bug is created. |