Problem on Linux Mint 22.3

[boss]

The UMS.conf file which UMS uses in NOT the file located in: /opt/ums-15.6.0/
The UMS.conf file which UMS uses IS the one located in: /home/david/.config/UMS/

You are correct about the UMS.conf file I sent. It was the wrong one sorry.
The correct one is attached now.

Your system ffmpeg is not configured with everything it needs and also it has an error: "WARNING: library configuration mismatch".
UMS has ffmpeg built in and for now, it would be easiest to configure UMS to use the built in one and see how that goes.

To do that, /home/david/.config/UMS/UMS.conf needs to be edited. (NOT /opt/ums/ums-15.6.0/UMS.conf)
Look for the line: ffmpeg_path = (that means it will use your mint ffmpeg)
To use the UMS inbuilt ffmpeg, change that line or add it if it does not exist to: ffmpeg_path = /opt/ums-15.6.0/linux/ffmpeg/

See how that works out for you.

[iamthebull]

I initially tried adding ffmpeg_path = /opt/ums-15.6.0/linux/ffmpeg/ to my existing /home/david/.config/UMS/UMS.conf file. Same error. I then replaced my UMS.conf with the one you sent. It still crashed and gave a slightly different output but still related to malloc. The log file attached was for the second case using your UMS.conf.

Code: Select all

Fatal glibc error: malloc.c:2599 (sysmalloc): assertion failed: (old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)
Aborted (core dumped)

debug.log.zip

(78.16 KiB) Downloaded 647 times

[boss]

You probably are, but just to check: You do stop UMS, make the changes and then start UMS again?
After you replaced: /home/david/.config/UMS/UMS.conf with the one I sent, did you modify the line:
ffmpeg_path =
To
ffmpeg_path = /opt/ums-15.6.0/linux/ffmpeg/
In the UMS.conf that I sent?

If you did do that, the next thing I would try is to remove "file": "/media/shared/Music", from SHARED.conf
And replace with a folder which has some videos.
This is to check if something in your Music folder is causing the issue.

PS: I just rechecked the log file you sent (when using the UMS.conf that I sent you).
It looks like UMS is using your system ffmpeg.
From the log: DEBUG 2026-06-26 08:45:02.900 [main] Starting /usr/bin/ffmpeg -hwaccels
Try changing it how I described above to use the UMS supplied ffmpeg.
EG: ffmpeg_path = /opt/ums-15.6.0/linux/ffmpeg/

The output of your system ffmpeg says: DEBUG 2026-06-26 08:45:02.972 [ffmpeg-1-2] WARNING: library configuration mismatch

Information about this error is:
The WARNING: library configuration mismatch error occurs because your main ffmpeg binary was compiled with different configuration flags
than the underlying shared libraries (libavcodec, libavutil, libavformat, etc.) currently loaded on your system.
This usually happens after an incomplete package update, when using conflicting
Third-Party PPAs, or when multiple versions of FFmpeg are installed simultaneously.While FFmpeg will often continue to run despite this
warning, it can cause unpredictable crashes, broken hardware acceleration, or missing codecs.

[mik_s]

I'm sceptical that it could be a FFmpeg problem since it is happening during the media scan.
If it was a video then FFmpeg would be used to create a thumbnail but all these are MP3s.

There are some errors but are just because part of the scan checks for images and since MP3s are not images it says "Unable to recognize image format" and causes an exception error, but this should not effect anything and is ignored.

@boss is there any system logging on Linux that could reveal more as there is no signs within UMS itself. I think I remember you doing something about backtrace or memory dump logs before.

The change in the error message from

Code: Select all

malloc(): corrupted top size

to

Code: Select all

Fatal glibc error: malloc.c:2599 (sysmalloc): assertion failed: ...

may mean a physical problem with your memory.
Have you ever had problems with odd behaviour on your system?

Several years ago on my old computer I started having all sort of random problems and frequent blue screen with unrelated errors each time.
Someone mentioned running a ram test and I found that one of my sticks was faulty. Removing it was enough stop the errors and I eventually replaced both of them.
I had a i5-2500 CPU which is not that much older than your i7-4770K and if you are still using the same ram from when you got it they just might be failing.
I don't know how well Linux can handle memory problems so it may recover instead of blue screening like in Windows.

See if there is a memory testing program for Linux you can run just to confirm or rule this out.

[boss]

@mik_s & @iamthebull

Many years ago, I had a problem (can't remember if it was making UMS crash) when using my system ffmpeg.
But... when using ffmpeg supplied with UMS there was no problem.
In the end I recompiled my system ffmpeg so that the options in the UMS included ffmpeg were in my system ffmpeg.
I think it is worth editing UMS.conf to use the inbuilt UMS ffmpeg just to discount the system ffmpeg being an issue. Won't do any harm.

That said, I do believe it is a computer/system problem.
Either something is triggering that or their is some physical/configuration problem with the computer.

MEMORY
I've not had any problems with my linux servers related to memory except in relation to the "Out of memory - Java heap size error" in earlier versions of UMS.
There is a program named "stress" which can be used to check many components in a linux computer under stress including memory.
I haven't used Linux Mint specifically but I believe it is installed by:
sudo apt install stress

Once installed, you can test the computers memory by:
stress --vm 2 --vm-bytes 2GB --timeout 2m

I see the Mint computer has 16GB of RAM. It will run on 8GB fine so if you have 2 x 8GB sticks of RAM, you could also test using just one 8GB stick at a time.

[iamthebull]

@boss

Yes I did set ffmpeg_path = /opt/ums-15.6.0/linux/ffmpeg/ in your copy of the UMS.conf file. If you look in the log file you will see the following:

Code: Select all

DEBUG 2026-06-26 08:45:03.001 [main] Custom executable path for FFmpegProgramInfo FFmpeg: [installed = "FFmpegExecutableInfo [executablePath=/usr/bin/ffmpeg, available=null, version=null, errorType=null, errorText=null, protocols=null]", (*)custom = "FFmpegExecutableInfo [executablePath=/opt/ums-15.6.0/linux/ffmpeg, available=null, version=null, errorType=null, errorText=null, protocols=null]"] was initialized to "/opt/ums-15.6.0/linux/ffmpeg"
DEBUG 2026-06-26 08:45:03.136 [main] /usr/bin/ffmpeg supported protocols: [async, bluray, cache, concat, concatf, crypto, data, fd, ffrtmphttp, file, ftp, gopher, gophers, hls, http, httpproxy, https, mmsh, mmst, pipe, rtmp, rtmps, rtmpt, rtmpts, rtp, sctp, srtp, subfile, tcp, tls, udp, udplite, unix, amqp, rist, srt, sftp, zmq, ipfs, ipns, mms]
DEBUG 2026-06-26 08:45:03.162 [main] /opt/ums-15.6.0/linux/ffmpeg supported protocols: [async, bluray, cache, concat, concatf, crypto, data, fd, ffrtmpcrypt, ffrtmphttp, file, ftp, gopher, gophers, hls, http, httpproxy, https, mmsh, mmst, pipe, rtmp, rtmpe, rtmps, rtmpt, rtmpte, rtmpts, rtp, srtp, subfile, tcp, tls, udp, udplite, unix, rist, srt, sftp, zmq, ipfs, ipns, mms]

It is aware of the system ffmpeg (ie. executablePath=/usr/bin/ffmpeg) and also it reports to be initializing a custom executable path to /opt/ums-15.6.0/linux/ffmpeg. Maybe the two are conflicting with each other somehow?

I am restarting the server each time I am making changes mostly by default since UMS is crashing.

@mik_s I haven't had any problems with odd behavior on this system. I'll check out the memory tests and report back.

[iamthebull]

I'm sceptical that it could be a FFmpeg problem

I will second that motion. Note that originally ffmpeg was not installed on my system. It was not until @boss asked me to confirm the package versions that I installed ffmpeg in the first place. In the first log file I included it has:

Code: Select all

TRACE 2026-06-24 20:12:01.761 [TPW "ffmpeg" 2] Executing "/opt/ums-15.6.0/linux/ffmpeg -y -f lavfi -i nullsrc=s=720x480:d=1:r=1 -vf ass=DummyInput.ass -target ntsc-dvd -"
DEBUG 2026-06-24 20:12:01.767 [main] Starting /opt/ums-15.6.0/linux/ffmpeg -hwaccels
TRACE 2026-06-24 20:12:01.768 [Process Terminator] ProcessTerminator scheduled shutdown of process "ffmpeg" in 300000 milliseconds
TRACE 2026-06-24 20:12:01.768 [Process Terminator] ProcessTerminator scheduled shutdown of process "mplayer" in 300000 milliseconds
TRACE 2026-06-24 20:12:01.768 [Process Terminator] ProcessTerminator is waiting 299999 milliseconds
DEBUG 2026-06-24 20:12:01.769 [main] Process ID (/opt/ums-15.6.0/linux/ffmpeg): 37985
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2] ffmpeg version N-119615-gf414038779-20250520 Copyright (c) 2000-2025 the FFmpeg developers
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   built with gcc 15.1.0 (crosstool-NG 1.27.0.42_35c1e72)
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-zlib --enable-libfribidi --enable-gmp --enable-libxml2 --enable-openssl --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libfreetype --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libdvdread --enable-libdvdnav --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-libzmq --enable-lv2 --enable-libvpl --enable-openal --enable-liboapv --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libvvenc --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-libs='-ldl -lgomp' --extra-ldflags=-pthread --extra-ldexeflags=-pie --cc=x86_64-ffbuild-linux-gnu-gcc --cxx=x86_64-ffbuild-linux-gnu-g++ --ar=x86_64-ffbuild-linux-gnu-gcc-ar --ranlib=x86_64-ffbuild-linux-gnu-gcc-ranlib --nm=x86_64-ffbuild-linux-gnu-gcc-nm --extra-version=20250520
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libavutil      60.  2.100 / 60.  2.100
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libavcodec     62.  3.101 / 62.  3.101
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libavformat    62.  0.102 / 62.  0.102
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libavdevice    62.  0.100 / 62.  0.100
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libavfilter    11.  0.100 / 11.  0.100
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] Hardware acceleration methods:
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libswscale      9.  0.100 /  9.  0.100
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-2]   libswresample   6.  0.100 /  6.  0.100
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] cuda
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] vaapi
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] qsv
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] drm
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] opencl
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] vulkan
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] amf
DEBUG 2026-06-24 20:12:01.782 [ffmpeg-1-1] 

which clearly shows UMS using the packaged ffmpeg package in /opt/ums-15.6.0/linux/ffmpeg

I used Memtest86+ to do a memory scan and there were no errors with 2 passes.

When performing the media scan is UMS creating some kind of data structure internally that represents my media library? If so, maybe that data structure is growing too big while scanning my Music folder and that's causing issues? I wouldn't think of my music library as being all that relatively large (~3000 files).

I tried again with my TV Shows folder (approx 1000 items) in place of my Music folder and there were no issues.

[iamthebull]

If so, maybe that data structure is growing too big while scanning my Music folder and that's causing issues?

Continuing on this line of thought I decided to do some further testing. In my music folder there are 7 folders:

Code: Select all

david@Desktop1:~/.config$ ls /media/shared/Music/
Albums  CDs  Christmas  Comedy  Singles  Striker  Unsorted

I added each of these one at a time to see if adding fewer items at a time would help. Test steps:

1. deleted ~/.config/UMS - clean start
2. launched UMS and added CDs folder (the largest one) and triggered a scan - no problems
3. added Albums folder and triggered a scan - CRASH
4. deleted ~/.config/UMS - clean start
5. launched UMS and added Christmas folder and triggered a scan - no problems
6. added Comedy folder and triggered a scan - no problems
7. added Singles folder and triggered a scan - CRASH
8. deleted ~/.config/UMS - clean start
9. launched UMS and added Striker folder and triggered a scan - no problems
10. added Unsorted folder and triggered a scan - no problems
11. added Singles folder and triggered a scan - no problems (note: last time UMS crashed adding this folder)
12. added the rest of the folders one at a time and triggering a scan after each - no problems

So now I have managed to add my entire Music library without UMS crashing. I even browsed the server with a client and played a track from each folder with no issues. This leaves me thinking that it's not an issue with the media content itself and leaves me more convinced that there's an issue with how UMS is managing the data it's collecting from the media scan internally. Thoughts?

[boss]

I have done some research in regard to the "malloc():" errors and checked out some forums in relation to that error.
It seems that the highest probability that this error is happening is that UMS is trying to write information beyond the memory bounds of your system.
Or
Possibly but less likely, there is an issue with GLIBC on your Linux Mint system.

As a test, you could try installing an earlier version of UMS and see if that resolves the issue.
The earlier version should be V12 or greater as the configuration files are a bit different prior to V12.
With V12 or greater, your existing configuration files in "/home/david/.config/UMS/" don't need to be changed.
Perhaps try "UMS-13.0.0-x86_64.tgz" from: https://www.videohelp.com/software/Univ ... d-versions

It's a minor job to install that earlier version and I believe it would be well worth doing as a test.

If the error still occurs with the earlier version of UMS, I will give you a copy of a program named DMS (Digital Media Server) which is a fork of UMS (but based on a much earlier version) to do a test.

Hopefully we can get to the bottom of things.

[iamthebull]

I tried UMS-13.0.0 as you suggested and the media scan completed without any problems.