More > JRiver Media Center 30 for Linux
JRiver Media Center 30.0.67 for Debian Buster (amd64, i386, arm64 and armhf)
mwillems:
--- Quote from: bob on March 01, 2023, 09:27:57 am ---Where is the library?
--- End quote ---
It's a client to a remote server so I think it's using the server's library? I was wondering if this might be related to the new delta sync stuff introduced in 55 since the issue went away when going back to 51. It seemed to happen at track change when the client reached back to update the server on play counts.
--- Quote ---Do you have any handheld devices?
--- End quote ---
None that are attached.
--- Quote ---How about any CD's?
--- End quote ---
None in the drive
--- Quote ---You might try running it under gdb. It will provide a stack backtrace on crash even if it's not a full symbolic one that info can be useful
Install gdb (on debian: sudo apt-get install gdb)
Then from a command line as the normal user
gdb mediacenter30
When it loads you do
run
When it crashes you can get a stack trace by doing
bt full
--- End quote ---
I'll try that tonight when I'm off work and post back.
bob:
--- Quote from: mwillems on March 01, 2023, 09:31:55 am ---It's a client to a remote server so I think it's using the server's library? I was wondering if this might be related to the new delta sync stuff introduced in 55 since the issue went away when going back to 51. It seemed to happen at track change when the client reached back to update the server on play counts.
None that are attached.
None in the drive
I'll try that tonight when I'm off work and post back.
--- End quote ---
Thanks, I suspect you are probably correct about the delta stuff. It was pretty complicated. I'll warn them that something might be coming their way.
lepa:
FileFolder() function seems to give wonky results in especially in Linux. Seems to count from wrong direction as far i could understand its faulty logic
lepa:
Now when looking at the docs, it looks that filefolder works from right to left. From the other thread I assumed the other way round and didn't check the docs. So it seems to work just fine
mwillems:
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!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version