Synology DS1618+ A fatal error has been detected by the Java Runtime Environment

[LBKirk]

I'm sorry if I missed the fix for this in another thread but the ones I found didn't seem to help but all of a sudden this error started a few weeks ago. I hadn't updated anything during that time and this just randomly started happening. I believe the issue is related to too many files. I have managed to kind of get it back working by cleaning out the folder that Filebot is scheduled to check every couple hours and making sure it only has no more than maybe 20 files and sometimes it gets the error then. As far as a little background info, I use Filebot Node to originally set up a scheduled task in the Synology Task Scheduler which runs every couple hours. My Synology is a DS1618+ that uses an Intel Atom C3538 cpu with 32GB or ram and ample hard disk space. It's currently running DSM 7.2.2-72806 Update 1. I'm running Filbot version 5.1.6 with Filebot Node 0.4.7. I'm pasting one of the log output files below and Thank you very much for any guidance.

Code: Select all

Run script [fn:amc] at [Sun Jan 12 11:00:06 EST 2025]
Parameter: ut_label = TV
Parameter: artwork = y
Parameter: subtitles = eng
Parameter: clean = y
Parameter: skipExtract = y
Parameter: minLengthMS = 300000
Parameter: seriesFormat = { plex }
Parameter: seriesDB = TheTVDB
Parameter: excludeList = .excludes
Argument[0]: /volume2/complete/TV Shows
Use excludes: /volume1/TV Shows/.excludes (6)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f40f07e418c, pid=346, tid=360
#
# JRE version: OpenJDK Runtime Environment Temurin-21.0.3+9 (21.0.3+9) (build 21.0.3+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (21.0.3+9-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libmediainfo.so+0x5e418c]  MediaInfoLib::File_Avc::sei_message_user_data_registered_itu_t_t35_GA94_03_Delayed(unsigned int)+0x2bc
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/syno/sbin/syno-dump-core.sh /volume1 %p %s %P" (or dumping to /run/synoscheduler/workspace/admin/core.346)
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid346.log
[7.329s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/usr/local/bin/filebot: line 55:   346 Aborted                 (core dumped) java -Dapplication.deployment=spk -Dnet.filebot.license="$FILEBOT_LICENSE" -Dnet.filebot.media.parser="$MEDIA_PARSER" -Dnet.filebot.media.ffprobe="$FFPROBE" -Dnet.filebot.archive.extractor="$ARCHIVE_EXTRACTOR" -Dnet.filebot.archive.7z="$P7ZIP" -Dnet.filebot.archive.unrar="$UNRAR" -Djava.awt.headless=true --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.function=ALL-UNNAMED --add-opens=java.base/java.util.regex=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.nio.file=ALL-UNNAMED --add-opens=java.base/java.nio.file.attribute=ALL-UNNAMED --add-opens=java.base/java.nio.channels=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.time=ALL-UNNAMED --add-opens=java.base/java.time.chrono=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.text=ALL-UNNAMED --add-opens=java.base/sun.nio.fs=ALL-UNNAMED --add-opens=java.logging/java.util.logging=ALL-UNNAMED --add-opens=java.desktop/java.awt=ALL-UNNAMED --add-opens=java.desktop/sun.awt=ALL-UNNAMED --add-opens=java.desktop/sun.swing=ALL-UNNAMED --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED -XX:+DisableAttachMechanism -Djna.boot.library.path="$LIBRARY_PATH" -Djna.library.path="$LIBRARY_PATH" -Djava.library.path="$LIBRARY_PATH" -Dapplication.dir="$APP_DATA" -Dapplication.cache="$APP_DATA/cache" -Dfile.encoding="UTF-8" -Dsun.jnu.encoding="UTF-8" -Duser.home="$APP_DATA" -Djava.util.prefs.PreferencesFactory=net.filebot.util.prefs.FilePreferencesFactory -Dnet.filebot.util.prefs.file="$APP_DATA/prefs.properties" -Dnet.filebot.util.prefs.sync=false $JVM_OPTS $JAVA_OPTS $FILEBOT_OPTS -jar "$FILEBOT_HOME/jar/filebot.jar" "$@"

[rednoah]

libmediainfo is crashing the process:

Code: Select all

# C  [libmediainfo.so+0x5e418c]  MediaInfoLib::File_Avc::sei_message_user_data_registered_itu_t_t35_GA94_03_Delayed(unsigned int)+0x2bc

What does filebot -script fn:sysinfo say? (i.e. Tools ➔ System Information)


How did you install libmediainfo? (see Optional Features)


If you believe the problem to be caused by a specific file that leads libmediainfo to crash, then you'll want to remove that file. You can systematically narrow down on that file or files by running on different folders (i.e. binary search) and seeing what happens. Setting --def minLengthMS=0 might help you find or at least ignore the offending file.


filebot can be configured to use ffprobe instead of libmediainfo to read basic media information (e.g. video duration) from video files.


You may find more information about what exactly each thread was doing at the time in this log file:

Code: Select all

# An error report file with more information is saved as:
# /tmp/hs_err_pid346.log

[LBKirk]

Here is what filebot -script fn:sysinfo states:
FileBot 5.1.6 (r10435)
JNA Native: 7.0.0
MediaInfo: 19.04
Tools: 7z/16.02 unrar/5.70
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2024-10-16 (r986)
Groovy: 4.0.21
JRE: OpenJDK Runtime Environment 21.0.3
JVM: OpenJDK 64-Bit Server VM
CPU/MEM: 4 Core / 8 GB Max Memory / 34 MB Used Memory
OS: Linux (amd64)
HW: Linux judrep-rem-bu01 4.4.302+ #72806 SMP Thu Sep 5 13:43:08 CST 2024 x86_64 GNU/Linux synology_denverton_1618+
CPU/MEM: : Intel(R) Atom(TM) CPU C3538 @ 2.10GHz / MemTotal: 33 GB / MemFree: 804 MB / MemAvailable: 14 GB / SwapCached: 11 MB / SwapTotal: 22 GB / SwapFree: 5 MB
STORAGE: ext4 [/] @ 6 GB | btrfs [/volume1] @ 98 TB | btrfs [/volume2] @ 47 TB
UID/GID: uid=1026(XXXXXXX) gid=100(users) groups=100(users),101(administrators)
DATA: /var/packages/filebot/var/data/1026
Package: SPK
License: FileBot License XXXXXXX (Valid-Until: 2069-07-19)
Done ヾ(＠⌒ー⌒＠)ノ

I far as how I installed Filebot I just went to Synology package center added https://get.filebot.net/syno/ to my packages sources installed java, Filebot, and Filebot Node. Then it made me install Node.js from the Synology packages which is on version 18. I don't see libmediainfo installed in my packages so I'm not sure if that is just on Synology by default or if its possible it was built into Filebot. Could this be the issue? I completely started fresh with this nas 6 months ago and FB had worked perfect with no issues until Dec and I thought the exact same thing about it being a corrupt file or something so I kept trying different chunks and it only seemed to matter if there were a lot of files at the time the script ran. It could very well just be coincidence but I figured worth noting.

Thank you for your help. It's very much appreciated

Did you want me to post the contents of the hs_err_pid346.log log file also?

[LBKirk]

I think it may have been the lack of an updated mediainfo from the Synology package Center has fixed the issue. I do remember having it installed on this nas before I had to rebuild it but for some reason FB had been working like a champ for 6 months without it. I assuming there was some version on the nas by default or something. Regardless after updating it I moved th huge chunk of files to the folder and ran the task in it would normally of crashed almost immediately but now it seems to be good. Sorry for wasting your time but again thank you.

[rednoah]

I don't see libmediainfo installed in my packages so I'm not sure if that is just on Synology by default or if its possible it was built into Filebot. Could this be the issue?

FileBot includes a generic Linux libmediainfo.so but it may not be perfect / compiled for the specific CPU architecture you're using. Should work, but if it doesn't you can try a different one. The SynoCommunity package is more up-to-date and compiled for your specific CPU arch using the Synology compiler toolchains. Might work better.

[LBKirk]

I mistakenly said from the Synology packages for the mediainfo location but I meant it was from the SynoCommunity packages. I ran several tests trying to break it and it's worked perfect ever since. Filebot is by far the most reliable, consistent, and just the perfect app which I'm very grateful for. Keep up the good work and thanks again for the immediate 5 Star support.