View Issue Details

IDProjectCategoryView StatusLast Update
0014720MMW 5Playlists (Auto) / Search / Filterspublic2018-12-20 21:33
Reporterrusty Assigned To 
PriorityurgentSeveritycrashReproducibilityalways
Status closedResolutionreopened 
Product Version5.0 
Target Version5.0Fixed in Version5.0 
Summary0014720: Various CPU intensive triggers --> Uncaught Error: "We haven't got lock for 3 seconds!"
DescriptionWhen I initiated a contextual search in the Music node, the Uncaught Error: "We haven't got lock for 3 seconds!" error occured.

Once that error occurred, the hourglass was spinning endlessly and 'Reading files' appeared endlessly in the lower left corner.

See attached image.
TagsNo tags attached.
Attached Files
Fixed in build2138

Relationships

related to 0015258 closedpetr CPU Utilization sometimes stays at 50% on certain nodes 
related to 0014722 closedLudek Contextual search fails when apostrophe is included 

Activities

Ludek

2018-04-11 14:09

developer   ~0049916

Fixed in 2096

rusty

2018-04-13 01:36

administrator   ~0049943

Can't replicate in 2096. Resolving.

rusty

2018-12-06 19:51

administrator   ~0051683

Last edited: 2018-12-06 20:29

As reported at 0015240:0051677, I've been able to replicate the 'We haven't got lock for 3 seconds' 2 times via the following steps (I can't replicate it consistently):
1 Initiate wi-fi sync
2 Once the sync starts, navigate the content tree in 'Auto-Sync (--> Device)', e.g. click music and then expand 'Artist'
--> it takes some time for the tree to appear (MM shows 'loading' in the status bar) and then crashes with an elog dialog and a white screen.

Here's a crashlog ID: A8695FB0
Here's a second crashlog created with a custom build provided by Ludek: 852C7049

Debug log attached.

Note: I was navigating the tree while a Wi-Fi sync operation to the device in question was in progress. Not sure if that wast he cause of the crash.

Ludek

2018-12-07 09:23

developer   ~0051689

Last edited: 2018-12-07 10:53

We have made some changes that should either stop the issues from appearing or give us more info in case this re-occurs

Please test with 2138+ and submit another log (in case this re-occurs)

rusty

2018-12-10 01:37

administrator   ~0051714

Unable to replicate with 2138, but will re-open this bug if it recurs.

peke

2018-12-11 00:39

developer   ~0051732

Verified 2138

rusty

2018-12-20 21:33

administrator   ~0051843

I can confirm that this hasn't occurred in the last several builds. Closing.