More > JRiver Media Center 24 for Linux
MediaCenter24 Crashing in Linux
bob:
--- Quote from: Dexos on October 03, 2018, 06:26:28 pm ---Thank you Bob and Jim for your great ideas. Both of your suggestions were great additions for things to keep eliminating.
But we have an answer. At least the beginnings of an answer.
Yet another clean install, Mint with Mate this time. I was getting tired of the Debian and as the problem followed me across distros I should be safe!!
ran full import with Media Centre and ensured that it was the only computer on my network at the time. (This is getting extreme!). Played must for an hour with out a crash. If it was going to crash it was going to happen within 5 minutes of starting JRiver.
Then I turned on my Windows computer. another 20 minutes of music, no problem. Next I turned on one of my Ugoos UT3+(1 of 2) Android devices. 3 minutes passed and BANG! There is the crash. Turn UT3+(1 of 2) off and JRiver keeps running.
Next lets find out of this happens to UT3+(2 of 2) Guess what/ This one does not cause the problem.
The difference between these 2 devices is that I recently installed a Beta OS Upgrade from Android 5.1.1 to Android 7.1.2. The new OS Appears to have 2 native DLNA Renderer services installed and running at startup. One of the 2 I can not turn off, and the second appears not to be running at the moment but keeps turning itself back on.
Solution for me is I will downgrade the OS and hope that some time in the future the problem is resolved by either us in JRiver or them on their Android platform.
Quick disclaimer!! I am not knocking Ugoos. Technology is complicated and I expect these things from time to time. Ugoos is a brand I have been using for ages. I have bought other brands but have come back because of the quality hardware. I recommend to anyone (Not running JRiver at the moment to pick one up.) It has an optical out that from my perspective gives me digital as close to the amp as I can get it. Has been rock solid and stable. The other is in my bedroom and is my morning alarm clock.
--- End quote ---
Thanks for the detailed report.
This sounds very similar to an issue we solved with a Android app earlier. It's probably going to take getting something like that running here so we can catch it in the debugger.
Dexos:
--- Quote from: bob on October 04, 2018, 10:42:20 am ---Thanks for the detailed report.
This sounds very similar to an issue we solved with a Android app earlier. It's probably going to take getting something like that running here so we can catch it in the debugger.
--- End quote ---
What I should not have done was downgrade the android box so quickly. I could upgrade the device again if we think a review of a tcpdump would help.
Dexos:
--- Quote from: bob on October 04, 2018, 10:42:20 am ---Thanks for the detailed report.
This sounds very similar to an issue we solved with a Android app earlier. It's probably going to take getting something like that running here so we can catch it in the debugger.
--- End quote ---
What was the application that caused the issue. I believe that in my case it was an app called "eHomeMediaCenter"
I am only partially sure of that. There was also a "DLNA" app that was also packaged with the upgraded OS.
bob:
--- Quote from: Dexos on October 04, 2018, 08:52:01 pm ---What was the application that caused the issue. I believe that in my case it was an app called "eHomeMediaCenter"
I am only partially sure of that. There was also a "DLNA" app that was also packaged with the upgraded OS.
--- End quote ---
This was the thread from May:
https://yabb.jriver.com/interact/index.php/topic,113536.0.html
Maybe check that out and see if any of it might apply?
If you could run a windows build and reproduce the crash we might get a useful dump file. That's how we tracked the last one down.
Navigation
[0] Message Index
[*] Previous page
Go to full version