View Issue Details

IDProjectCategoryView StatusLast Update
0007462MMW v4Playlist / Searchpublic2011-03-10 22:27
Reporterrusty Assigned To 
PriorityimmediateSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Product Version4.0 
Target Version4.0Fixed in Version4.0 
Summary0007462: 1351 Performing searches --> freeze
DescriptionWhen downloading podcasts (tested with videopodcasts in this case), if the user attempts to search the video node (tested using Search 'current selection') with Art View active, --> MM freezes.

Important: performing the same searches on the same node in Details view doesn't trigger the freeze.

See updated comment--the bug occurs even when podcasts aren't being downloaded.

Debug log attached.
TagsNo tags attached.
Attached Files
Fixed in build1352

Activities

rusty

2011-03-03 22:38

administrator   ~0023556

Note: this issue occurs even when MM is not downloading a podcast.

rusty

2011-03-03 22:43

administrator   ~0023557

Last edited: 2011-03-03 23:24

Note: I was able to trigger an AV on XP (instead of a freeze). It resulted in an error log being submitted. (I've sent 3-4 such error logs).

rusty

2011-03-03 23:24

administrator   ~0023558

Upon further investigation, I can:
a) Trigger a freeze by Searching for a string in the quicksearch bar if i) In video node ii) if Search is set to 'Current Selection'
b) Trigger an AV by Searching for a string in the quicksearch bar and then deleting the search term if i) in video node ii) if Search is set to 'Current Collection'

Note that the problem _always_ occurs when view is set to Art/Art&Details, and only sometimes occurs when in details view.

Setting to 'immediate' due to the severity of this issue.

Ludek

2011-03-04 09:07

developer   ~0023564

From the attached log it looks like a slow tags reading for track
\\192.168.0.147\Qdownload\A Serious Man 2009 BRRip H264 AAC-GreatMagician\A Serious Man.mp4

e.g. F_AAC: parse_atoms() takes 7 seconds.

Ludek

2011-03-04 09:09

developer   ~0023565

As discussed over IM with Petr, based on the submitted Eureka Logs it was an error in Art Views and is fixed in 1352.

peke

2011-03-10 22:27

developer   ~0023644

Verified 1352