View Issue Details

IDProjectCategoryView StatusLast Update
0006604MMW v4Otherpublic2010-12-23 05:00
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
Product Version4.0 
Target Version4.0Fixed in Version4.0 
Summary0006604: UPnP related access violation
DescriptionOccasionally, upnp.dll will generate an AV when MM is running in the background. e.g. editing a document in word when MM is running but not playing anything.

Eurekalog debug log was submitted today.
TagsNo tags attached.
Attached Files
bug1.elf (77,885 bytes)
Fixed in build1335

Relationships

related to 0006969 closedLudek Update to the newest version of Platinum UPnP SDK 

Activities

Ludek

2010-10-29 09:11

developer   ~0021059

Last edited: 2010-10-29 11:08

Strange, you are saying that MM was only running on the background without doing anything? No server was accessing MM UPnP server at the time?

I haven't seen the submitted log yet, but I would probably need to see standard log, I am about to enable advanced UPnP logging in build 1319.

Nevertheless there is a new version of Platinum SDK (0.6.1), we currently use (0.5.4). Maybe updating would fix the problem.

Ludek

2010-10-29 11:06

developer   ~0021060

Petr, could you please find the EL for me? Thanks.

petr

2010-10-29 14:23

developer   ~0021061

Uploaded (sent by mail as well).

rusty

2010-11-09 13:19

administrator   ~0021270

Cannot reproduce in 1323.

rusty

2010-12-13 23:38

administrator   ~0021797

AV in upnp.dll occurs in build 1334. Elog submitted.

Ludek

2010-12-18 20:50

developer   ~0021913

Last edited: 2010-12-18 20:53

Hopefully fixed in 1335 by upgrading to the newest version of Platinum SDK ( 0006969 )

rusty

2010-12-19 02:54

administrator   ~0021915

Last edited: 2010-12-19 03:07

Tested 1336, and I still see such errors. e.g. Error Removing Prepared Query + AV. These AVs were generated when switching from the UPnP node to the Locations node. Submitted elogs for this for build 1336.

Edit: MediaMonkey crashed completely--the elogs were not submitted.

Ludek

2010-12-20 10:54

developer   ~0021956

It looks more like 0006866.
Could you please describe more detailed steps to repro?
I cannot reproduce and without the logs it is hard to guess what is going on.

rusty

2010-12-23 05:00

administrator   ~0022088

Verified 1340.