More > JRiver Media Center 30 for Linux
JRiver Media Center 30.0.67 for Debian Buster (amd64, i386, arm64 and armhf)
bob:
--- Quote from: mwillems on March 01, 2023, 04:41:32 pm ---Ok, so I reproduced the crash in gdb and I've attached a full log of the gdb session. The back trace starts around line 2090. I also simultaneously ran MC's internal logger just in case being able to compare the two might be helpful, and have attached a fresh log of the same session.
To describe exactly how it "looks" from the user side, the UI freezes in the second before the track changes, but MC starts playing the next song even though the UI is frozen. Then about twenty or so seconds into the second song it crashes.
Hopefully this helps and let me know if you need any additional logging/testing!
--- End quote ---
Thanks. The first thing I noticed is that there is huge number of threads running.
How big is your DB?
Do you have TV entries in it?
This is a linux client and windows server?
Version of MC on the windows server is?
You can get rid of the pretty annoying and useless thread switching messages in gdb by doing this in gdb before you run
set print thread-events off
mwillems:
--- Quote from: bob on March 02, 2023, 09:21:29 am ---Thanks. The first thing I noticed is that there is huge number of threads running.
How big is your DB?
Do you have TV entries in it?
This is a linux client and windows server?
Version of MC on the windows server is?
You can get rid of the pretty annoying and useless thread switching messages in gdb by doing this in gdb before you run
set print thread-events off
--- End quote ---
It's a linux client and a linux server, both on build 67, both running debian stable. No windows PCs in the mix at all.
My db has 135,848 files in it, and yes I have TV entries (just the standard guide views that come with MC, I haven't done any customization to my knowledge). I use a HDHomerun Prime networked TV Tuner; the server pulls down the guide data and serves it to clients.
Just to be clear I have several other Linux clients attached to the same server that are all behaving normally with build 67. The main difference is that the working clients are running arch. The PC that's crashing is running debian stable (as is the server). The only other potential differences I can think of are hardware differences, but I'm not sure how relevant that would be.
bob:
--- Quote from: mwillems on March 02, 2023, 09:28:11 am ---Bob, this is a linux client and a linux server, both on build 67, both running debian stable. No windows PCs in the mix at all.
My db has 135,848 files in it, and yes I also use a HDHomerun Prime TV Tuner. The server pulls down the guide data and serves it to clients.
Just to be clear I have several other Linux clients attached to the same server that are all behaving normally with build 67. The main difference is that the working clients are running arch. The PC that's crashing is running debian stable (as is the server).
--- End quote ---
Thanks for the info.
I think there is something odd about the number of threads running.
What's the difference in installed memory in the crashing client vs the non-crashing ones?
mwillems:
--- Quote from: bob on March 02, 2023, 09:36:08 am ---Thanks for the info.
I think there is something odd about the number of threads running.
What's the difference in installed memory in the crashing client vs the non-crashing ones?
--- End quote ---
The crashing system has 12GB of RAM, the working systems have a range from 4GB up to 16GB.
Otherwise in terms of hardware, the only other notable things are that the crashing system has an old Sandy Bridge CPU (an i7-2600K) and it's by far the oldest CPU in the house. It's also the only system using NVidia graphics in the house.
Not sure what to say about the threads, but the crashing system does use a fair amount of DSP and convolution, so that might be part of what's making the threads?
JimH:
--- Quote from: mwillems on March 02, 2023, 09:47:16 am ---The crashing system has 12GB of RAM, the working systems have a range from 4GB up to 16GB.
Otherwise in terms of hardware, the only other notable things are that the crashing system has an old Sandy Bridge CPU (an i7-2600K) and it's by far the oldest CPU in the house. It's also the only system using NVidia graphics in the house.
--- End quote ---
There's a video problem that I think you're aware of here: https://yabb.jriver.com/interact/index.php/topic,135232.msg937100.html#msg937100
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version