New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max recursion level exceeded by playlist_update_in_progress callback #165
Comments
This is potentially fixed by 5a6470d. Are you able to test with it? |
Thank you very much! I have installed latest Mopidy-Spotify and pyspotify develop versions by:
I will keep Mopidy running for a few days and let you know. |
We managed to reproduce the issue with this fix in place too. The hunt On Fri, Jun 26, 2015, 23:01 Dāvis Mošenkovs notifications@github.com
|
Couldn't there be a bug in libspotify - calling |
I believe commit e06b96a might have fixed this. Please comment if this is not true, and this should be reopened. |
Thank you very much! I will test this and let you know! |
I have experienced some Mopidy crashed while using commit e06b96a. Those crashes did not write anything in stdout/stderr or mopidy.log. |
I don't see this particular max recursion error any more. I do still get segmentation faults during startup but they may be due to something else. EDIT: although this one looks related to the recent fix. And this new scary looking one. |
I still get Mopidy crashes without anything written to stdout/stderr or Mopidy logs. I will enable core dumps to get some details. |
Yeah, ditto. It seems like the max recursion issue is gone, but we have at least one other segfault that we all three have experienced now. |
I get two different ones. One related to starred playlists when my
|
Can you open two new issues with all the information you have on them? |
I shall do so when I return from holiday next week.
|
When using pyspotify==2.0.0 with Mopidy==1.0.5 and Mopidy-Spotify==2.0.0 (commit 70f27932cb in develop) Mopidy crashes after some time with stacktrace:
The problem occurred after playing Spotify and local tracks on Mopidy and afterwards stopping playback and leaving Mopidy running for some hours. This was observed several times ("randomly" without trying to reproduce the issue or understand what caused it). This was the first time this issue happened after enabling logging of Mopidy stdout/stderr to file (the exception/stacktrace is not written to Mopidy logfile). This happened on Raspbian (Raspberry Pi model B).
The text was updated successfully, but these errors were encountered: