2018-09-18, 12:06
@debutanker (from #0916):
~15 seconds.
@beeswax (from #0912):
~27 seconds.
Something has gone wrong with the kodi fileitems processing in #0912. My guess would be the range-based loops change.
Ping @Rechi.
And besides, all of the processing done when "Saving fileitems ..." is for nought as the filecache is pretty much broken - the filecache that is created and written to disk is never read. I have toyed with the idea of disabling the filecache completely in these builds as it's just wasted CPU - probably just as well I didn't otherwise it would have have hidden this new issue.
text:
08:27:43.530 T:139923666016384 DEBUG: CGUIMediaWindow::GetDirectory (videodb://tvshows/titles/)
08:27:43.530 T:139923666016384 DEBUG: ParentPath = [videodb://tvshows/titles/]
...
08:27:58.381 T:139923666016384 DEBUG: Saving fileitems [videodb://tvshows/titles/]
08:27:58.381 T:139923666016384 DEBUG: -- items: 12, sort method: 0, ascending: true
~15 seconds.
@beeswax (from #0912):
text:
08:14:03.071 T:140349584910464 DEBUG: CGUIMediaWindow::GetDirectory (special://profile/playlists/video/GrownupsTV.xsp)
08:14:03.071 T:140349584910464 DEBUG: ParentPath = [special://profile/playlists/video/GrownupsTV.xsp]
08:14:03.094 T:140349584910464 DEBUG: This query part contains a like, we will double backslash in the next field: LIKE '
08:14:29.825 T:140349584910464 DEBUG: Saving fileitems [special://profile/playlists/video/GrownupsTV.xsp]
08:14:29.835 T:140349584910464 DEBUG: -- items: 713, sort method: 0, ascending: true
~27 seconds.
Something has gone wrong with the kodi fileitems processing in #0912. My guess would be the range-based loops change.
(2018-09-12, 23:28)Milhouse Wrote: Build Details:
Ping @Rechi.
And besides, all of the processing done when "Saving fileitems ..." is for nought as the filecache is pretty much broken - the filecache that is created and written to disk is never read. I have toyed with the idea of disabling the filecache completely in these builds as it's just wasted CPU - probably just as well I didn't otherwise it would have have hidden this new issue.