-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
3.30.0 crashes #249
Comments
I've rolled back to 3.29 and it still crashes with the same message. This started after upgrading to 3.30 yesterday. |
I restored to a backup from before the upgrade, and can recreate the breakage introduced by 3.30. |
Looks like there is no memory available. |
I wasn't doing anything particular, just starting to play any song. |
I'm still experiencing this issue, the server is nowhere near OOM and the container is far from its limit. I don't think it's an OOM issue. |
Here's a slightly more detailed crash log. Edit: never mind, it's the same log, for some reason it's malformed. Maybe less butchered it.
|
By the way, did you set some constraint? (see https://docs.docker.com/config/containers/resource_constraints/) |
I have no resource constraints on the container, so it's got plenty of room to grow when it fails. |
Another question: do you play transcoded tracks? |
Yes, I play transcoded tracks. |
It seems to always happen when the 'love' feedbacks are queued to be sent. |
Ok, thanks for the valuable log file. I have found something bad in the code involved that is very likely to explain your crash. Will schedule a hotfix asap |
Thank you very much for the prompt fix. :) |
@abdulocracy can you update your docker image and confirm the problem is gone for you? |
I've updated, will test and let you know if the issue persists. |
I'm running 3.30.0 on Docker x64.
It crashes with the following logs repeatedly:
The text was updated successfully, but these errors were encountered: