For possibly more information on why the core is dumping (lol) try running jellyfin from the cli (probably just typing the path to the jellyfin executable and pressing enter)
If nothing interesting is printed, try adding strace before the jellyfin executable (Google strace, it intercepts all system calls and logs them) if that doesn't work tell strace to follow forks.
Other than that you could start using binary debugging tools to see what shared libraries jellyfin is looking for? Maybe run it in gdb...
Csv is for arcane software or if you don't know where it's going.
Hdf5 is for Matlab interoperability
Otherwise I use parquet (orc could also work, but I never actually use it). Sometimes parquet has problems with Pandas or polars but I've always been able to fix it by using pyarrow
Sounds like you may want to run chrome in docker or try using nix. Nix won't clean up your user data automatically but with a few tweaks could do it easily. Docker will completely prevent files from hanging around (if you don't mount your home directory in the container), but if you want to download files to your host is its a bit tricky.
Be not afraid, for I bring good news of a functioning CPU and memory, tools to inspect your disks, and as foretold in the time of the smartphone you may even still have Internet access to read all of the documentation.
Or slow down a complete scan, it would take a long time to scan all likely ports on a machine stealthily, and be quite obvious if that machine is set up as a honeypot.
For possibly more information on why the core is dumping (lol) try running jellyfin from the cli (probably just typing the path to the jellyfin executable and pressing enter)
If nothing interesting is printed, try adding strace before the jellyfin executable (Google strace, it intercepts all system calls and logs them) if that doesn't work tell strace to follow forks.
Other than that you could start using binary debugging tools to see what shared libraries jellyfin is looking for? Maybe run it in gdb...