View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018517 | MMW 5 | UPnP / DLNA | public | 2021-11-05 19:24 | 2024-09-22 20:35 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.2 | ||||
| Target Version | 5.0.2 | Fixed in Version | 5.1 | ||
| Summary | 0018517: Possible AV in UpNp.dll after PC wake up | ||||
| Description | Every now and then I get an AV in UpNp.dll when not doing anything UPnP related. In this particular instance, MM was running and the PC went into hibernation twice. I saw the error upon resuming the second time (though it may have occurred prior to the second hibernation). The full error is: Exception Access violation at address 0D2114E4 in module 'UpNp.dll'. Read of address 0000000000. in module at 0D75FFFB. Would you like to restart mMediaMonkey in Safe mode? Tested on build 2515 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3050 | ||||
|
|
It relates to the fact that "r_pc_wakeup" is sent twice now (from the Browser process to the Render process after returning from sleep/hibernation) But it was sent twice only on third attemp returning from hibernation. |
|
|
Fixed in 2516 + also added prevention for the double "pc weakup" message |
|
|
Verified 2516 Tetsed on Hibernation, Sleep and Hybrid Sleep. |
|
|
Re verified 2518 Done additional tests with Auto Power off, Forced Sleep/Hibernate. |
|
|
Based on logs from tickets # 3613 and # 3611 the crash in UPnP.dll after PC wake up could still happen. => Fixed in 5.0.3.2604 |
|
|
Re-opened: User from [Ticket # 6719] is still observing AV in UPnP.dll after PC wake up.. |
|
|
Fixed in 3050 |
|
|
Closing, No regressions on My PC and user has not reopened Ticket. |
