-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Corrupted session file causes plugin crash #934
Comments
No memory leaks there. That is just a generic message Kodi gives for unhandled errors in addon scripts. Looks like files were not fully written to disk when you hard reset the Pi. Session data looks to be empty, but other files that indicate that setup is done do exist. Reset the jf4kodi settings and database, complete the setup wizard and initial sync, then safely close Kodi and reboot (no forced reset). This should ensure all files are properly written to disk. Random loss of files and data is an expected consequence of forced resets or power interruptions in any computer system. |
Thanks for the reply.
|
I didn't see any obvious way that jf4kodi would get into a state where that error would get thrown, except for on-disk data corruption issues, be it caused by a unclean shutdown or otherwise. A single stacktrace like that would not cause a memory leak problem, but if the crashing script was repeatedly re-starting and then crashing it could. Either way, that crash and log output does not cause the potential memory leak, but can be caused by the following lockup and hard-reset. I see that you also have a 500 server error in your logs, tracking down what causes that one would likely be more worth-while. |
Describe the bug
When starting Kodi the below error message is shown in the Kodi log file. After a few hours (4-6) kodi locks up and needs to be hard reset. Running on Raspberry Pi 4
To Reproduce
Reboot/Start Kodi with JellyFin plugin
Expected behavior
No memory leak or errors in the log file
Logs
System (please complete the following information):
The text was updated successfully, but these errors were encountered: