2023-09-19, 15:58
Hmm, the buffering was a clue but your log shows Kodi still using XCURL:: DllLibCurlGlobal instead of CFileCache. And the log shows the errors causing the problem are like:
error <general>: CCurlFile::CReadState::XFILE::CCurlFile::CReadState::FillBuffer - (0x240edc36620) Failed: Timeout was reached(28)
So there is something weird going on with XCURL:: DllLibCurlGlobal. I was also using Kodi portable on Windows 10 and with buffering = 1 it worked fine - no XCURL:: DllLibCurlGlobal.
I'm not sure how much work you want to put in (I'm keen to try and figure this out) but could you possibly start a new clean portable Kodi install and just have 'plugin.audio.spotify'
(v1.3.6 NOT v.1.3.6-experimental) as the only addon. If that works you could gradually add more addons seeing if any of them cause problems.
And could you add some curl logging - under 'Enable component-specific logging/ - Specify component-specific logging...' select 'Verbose logging for the libcURL library'.
Thanks
error <general>: CCurlFile::CReadState::XFILE::CCurlFile::CReadState::FillBuffer - (0x240edc36620) Failed: Timeout was reached(28)
So there is something weird going on with XCURL:: DllLibCurlGlobal. I was also using Kodi portable on Windows 10 and with buffering = 1 it worked fine - no XCURL:: DllLibCurlGlobal.
I'm not sure how much work you want to put in (I'm keen to try and figure this out) but could you possibly start a new clean portable Kodi install and just have 'plugin.audio.spotify'
(v1.3.6 NOT v.1.3.6-experimental) as the only addon. If that works you could gradually add more addons seeing if any of them cause problems.
And could you add some curl logging - under 'Enable component-specific logging/ - Specify component-specific logging...' select 'Verbose logging for the libcURL library'.
Thanks