View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017748 | MMW 5 | Other | public | 2021-04-12 16:05 | 2024-11-04 20:36 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.4 | Fixed in Version | 5.0.4 | ||
| Summary | 0017748: Possible AV in UPnP.dll during casting to DLNA receiver | ||||
| Description | This error reported occurs for some users. Report with debug log is at: https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=98782 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2683 | ||||
|
|
I have never seen this error, but reading about it: When a system conflict between some Windows components occurs, the Microsoft Visual C++ Runtime error is displayed, suggesting you need to perform some of the steps from this article: https://windowsreport.com/microsoft-visual-c-runtime-library-error-r6025/ to solve it or have a look at https://windowsreport.com/microsoft-visual-c-runtime-error-windows-10/ Asked user via the forum. EDIT: The user indicated that SFC scan found some problems, so maybe it was the reason for this error |
|
|
Based on the info from logs [Ticket # 1110] the issue should be already fixed in our RC-8 update (together with a mem leak while playing to DLNA player 0017755 and further DLNA related fixes). Resolved (to be closed once user confirms the issue being fixed) |
|
|
Looks like it happened again another user reported it at https://www.mediamonkey.com/forum/viewtopic.php?p=489343#p489343 |
|
|
Fixed in 2515 Test note: I haven't replicated the error myself, but made some changes that hopefully prevents this error. |
|
|
Re-opened: User just confirmed UPnP.dll verison that fixes the problem... |
|
|
Fixed in 2516 |
|
|
Verified 2516 No regressions found, close after user confirmed with 2516+ |
|
|
Closing no new reports |
|
|
This error still can happen in some environments (tickets 4725 and 4257) In the ticket 4257 user confirmed that the error does not happen with debug version of UPnP.dll compiled using the newest Miscrosoft Visual Studio 2022 So using this DLL for the build 5.0.4.2663 and higher.. |
|
|
Verified 2663 No regressions found on my devices. |
|
|
Reopen user at Ticket # 4725 reported further crashes. Asking for new info before resolving. |
|
|
From the logs I can confirm that AV while casting to DLNA receiver is still occuring for some users. I've made some code revisions and changes in UPnP.dll that should fix the issue finally. => Fixed in 2671 |
|
|
Based on user from [Ticket # 4725] this can still happen.. |
|
|
I have been able to simulate it finally and made a fix in 2676. Sent the fixed UPnP.dll to the user from ticket 4725 in order to confirm. |
|
|
Alhough I've been able to simulate and fix previously -- user from [Ticket # 4725] experienced a crash in UPnP.dll after hours of casting again (build 2682, crash EB3F0000) I've made a code revision in UPnP.dll and made code changes that hopefully resolves it finally (in build 2683) |
|
|
Closed as Fixed in 5.0.4. No new reports from user and no similar reports afterwards. |
