mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
Server Seems to Crash When Trying to Use EPUB Reader #1891
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#1891
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @Saamoz on GitHub (Jul 20, 2020).
Originally assigned to: @barronpm on GitHub.
Describe the bug
Server seemed to crash after an indeterminate amount of time when reading a book on the new 10.6 epub viewer.
System (please complete the following information):
To Reproduce
Expected behavior
To be able to read the book without crashing
Logs
Although it says
unable to find the specified file, the book does open and I am able to read it for a little while. The crash happens later, in that case it happened at 10:42@dkanada commented on GitHub (Jul 20, 2020):
cc @barronpm since this could be a database issue
@cvium commented on GitHub (Jul 21, 2020):
We just need a new notification type
15aea76523/Emby.Server.Implementations/Activity/ActivityLogEntryPoint.cs (L231-L244)@dkanada commented on GitHub (Jul 21, 2020):
I wonder if we even need media-specific playback notifications.
@stale[bot] commented on GitHub (Nov 19, 2020):
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 nightlies, 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.