bug: "Unexpected Application Error! s is null" + Possible EventEmitter memory leak detected #245
Closed
2 tasks done
Labels
bug
Something isn't working
fix waiting for release
Fix has been committed and waiting for a release to be cut
Milestone
Please check existing knowledge before opening an issue
Describe the Bug
The app should scrobble all plays to Last.FM from Jellyfin when I am using the Gelli android playback client, but instead only the first song played gets scrobbled to Last.FM, and then the web UI of multi-scrobbler indicates a crash.
The live logs in docker don't seem to indicate a problem at the time of the crash, but no further plays after the first song and UI crash are sent to Last.FM.
After the first song completes playback in Gelli, the web UI of multi-scrobbler starts displaying this:
Gelli continues playing, this initial song gets scrobbled, multi-scrobbler's UI continues displaying the error, and eventually the docker logs show 'MaxListenersExceededWarning: Possible EventEmitter memory leak detected'. No further scrobbling happens at this point.
This is not an issue when playing music from the web browser client or Jellyfin Media Player (windows client), multi-scrobbler handles the initial and subsequent scribbles as it should. This only occurs when I play from Gelli, and only after updating to 0.8.8.
I had the same issue as #239 after updating my installation from somewhere around 0.7.0 to 0.8.8. Switching to the :edge release cleared that issue up, but this is when I noticed the Gelli-related crash.
Platform
Docker
Versions
Logs
Additional Context
I have tried playing other songs from other devices at the same time trying to reproduce this issue, but I can only get it to reliably occur when playing from Gelli.
If I'm watching the live output from Docker logs, the multi-scrobbler web UI flips over to showing the error I mentioned in the description (Unexpected Application Error! s is null) at approximately the same time that 'Incoming play state' appears in the Docker logs, when the song switches over on the Gelli client.
The text was updated successfully, but these errors were encountered: