Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.2.0
-
Fix Version/s: 2.2.0
-
Component/s: None
-
Labels:None
-
Originating Party:QA
-
Browser:Chrome
Description
Steps:
1. Have more than 5000 media files in Media Library.
2. Create a smart playlist, then set criteria ,modifier. Then set the limit as 5k items.
3. Click generate.
Result:
Several minutes after, nothing appears on the item container, and an error will be found:
"
Uncaught SyntaxError: Unexpected token F jquery-1.7.2.min.js:2
e.extend.parseJSON jquery-1.7.2.min.js:2
callback smart_playlistbuilder.js:433
(anonymous function) smart_playlistbuilder.js:194
f.Callbacks.o jquery-1.7.2.min.js:2
f.Callbacks.p.fireWith jquery-1.7.2.min.js:2
w jquery-1.7.2.min.js:4
f.support.ajax.f.ajaxTransport.send.d
"
1. Have more than 5000 media files in Media Library.
2. Create a smart playlist, then set criteria ,modifier. Then set the limit as 5k items.
3. Click generate.
Result:
Several minutes after, nothing appears on the item container, and an error will be found:
"
Uncaught SyntaxError: Unexpected token F jquery-1.7.2.min.js:2
e.extend.parseJSON jquery-1.7.2.min.js:2
callback smart_playlistbuilder.js:433
(anonymous function) smart_playlistbuilder.js:194
f.Callbacks.o jquery-1.7.2.min.js:2
f.Callbacks.p.fireWith jquery-1.7.2.min.js:2
w jquery-1.7.2.min.js:4
f.support.ajax.f.ajaxTransport.send.d
"
Activity
Hide
Cliff Wang
added a comment -
Permalink
It's fine to generate 4999 items, but fail at 5000
Show
Cliff Wang
added a comment - It's fine to generate 4999 items, but fail at 5000
This is what I observed on Cliff's machine. He had about 50k+ tracks of 10 secs. So in this case, our implicit 24 hr time limit didn't kick in( since 5000 * 10 sec is less then 24 hrs).
So it had to deal with all 5000 files when picking random from pool, editing and etc.
In real situation, this situation is less likely happened assume the average length of usual track is around 3 mins.
Based on this assumption, I implemented limit on number of items to 500.
So it had to deal with all 5000 files when picking random from pool, editing and etc.
In real situation, this situation is less likely happened assume the average length of usual track is around 3 mins.
Based on this assumption, I implemented limit on number of items to 500.
Show
James Moon
added a comment - This is what I observed on Cliff's machine. He had about 50k+ tracks of 10 secs. So in this case, our implicit 24 hr time limit didn't kick in( since 5000 * 10 sec is less then 24 hrs).
So it had to deal with all 5000 files when picking random from pool, editing and etc.
In real situation, this situation is less likely happened assume the average length of usual track is around 3 mins.
Based on this assumption, I implemented limit on number of items to 500.
Verified at Airtime 2.2.0+e01f86c:1350576328
Show
Cliff Wang
added a comment - Verified at Airtime 2.2.0+e01f86c:1350576328