View Issue Details

IDProjectCategoryView StatusLast Update
0018517MMW 5UPnP / DLNApublic2022-01-25 22:47
Reporterrusty Assigned To 
PriorityurgentSeveritycrashReproducibilitysometimes
Status closedResolutionfixed 
Product Version5.0.2 
Target Version5.0.2Fixed in Version5.0.3 
Summary0018517: Possible AV in UpNp.dll after PC wake up
DescriptionEvery 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
TagsNo tags attached.
Fixed in build2604

Relationships

related to 0015000 closedrusty MMW v4 Sync: Device scan do not find MMW server 
related to 0018584 closedLudek MMW 5 Task queue deadlock detected - crashlog 0AF10000 

Activities

Ludek

2021-11-05 19:51

developer   ~0065771

Last edited: 2021-11-05 20:05

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.

Ludek

2021-11-05 20:04

developer   ~0065772

Last edited: 2021-11-05 20:04

Fixed in 2516

+ also added prevention for the double "pc weakup" message

peke

2021-11-06 18:34

developer   ~0065785

Verified 2516

Tetsed on Hibernation, Sleep and Hybrid Sleep.

peke

2021-11-12 12:42

developer   ~0065889

Re verified 2518

Done additional tests with Auto Power off, Forced Sleep/Hibernate.

Ludek

2022-01-25 22:44

developer   ~0066761

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