mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Error in "MusicBrainz" #4615
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jagiella on GitHub (Feb 9, 2023).
Please describe your bug
Since a few weeks scanning the music library is slow and frequently leads to crash and restart of the jellyfin server.
Jellyfin Version
Other
if other:
10.9.0
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@gnattu commented on GitHub (Feb 9, 2023):
I'm using personal fork from master as well and also encounters this issue.
I ended up with commenting out artist search in
MusicBrainzArtistProvideras I do not need it and here's the patch:If you do rely on this then you need a proper fix.
@Bond-009 commented on GitHub (Feb 9, 2023):
This should have been fixed by #8833 which commit are you running?
@gnattu commented on GitHub (Feb 9, 2023):
The last commit I rebased on was
421b062ca4And my tree does contain #8833. My MusicBranz Config page has a url set to
https://musicbrainz.org@jagiella commented on GitHub (Feb 11, 2023):
Repo:
@jellyfin-bot commented on GitHub (Jun 12, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.