INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Mac => Topic started by: NFB on April 27, 2019, 06:04:00 pm
-
Long-time user, first-time poster here. I have licenses for versions 23, and 24 for Mac. I'm troubleshooting a repeated (about once a day) crash issue that has now been occurring for many months. It occurs during normal use, no particular apparent trigger behavior. The crash report always show EXC_BAD_ACCESS (SIGSEGV), similar to the symptoms described in https://yabb.jriver.com/interact/index.php?topic=107542.0.
A log file is attached for a crash on version 25. Within the last few days this has happened on 23, then I switched the machine to version 24 and the same error occurred, and then I downloaded the trial of version 25 and the same thing occurred. To isolate the problem, the system it's running on is now a clean install (no other software or customizations installed), of High Sierra on a Mac Mini:
Hardware Overview:
Model Name: Mac mini
Model Identifier: Macmini6,1
Processor Name: Intel Core i5
Processor Speed: 2.5 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 4 GB
Boot ROM Version: MM61.010E.B00
SMC Version (system): 2.7f1
Serial Number (system): C07LD4CNDWYL
Hardware UUID: 9F9CE49B-2E80-5913-BE4F-4B65EF0B7FFE
System Version: macOS 10.13.6 (17G65)
Kernel Version: Darwin 17.7.0
Boot Volume: Macintosh HD
Boot Mode: Normal
-
Thanks for all the information.
-
Can you post the full OSX crash report? The MC log unfortunately doesn't help much with crashes on Macs.
-
Sure, glad I captured one last night. This is from a different crash a few hours later, but the same error message.
-
Attaching another one that happened today. The last two times, the crash has occurred when clicking the "stop" button during a playing video.
-
Attaching another one that happened today. The last two times, the crash has occurred when clicking the "stop" button during a playing video.
What is the device on IP address 10.0.0.210?
I assume that this is not always upon playing video?
What is your video configuration (number of monitors, size, chipset)?
-
That is correct regarding the IP address.
It's not always when playing video, but it seems to happen more often when either tagging or playing video is involved. At least one of the crashes in the last several days occurred sometime overnight, while doing not anything.
When I mentioned that the issue has been happening for several months, it was formerly running on the iMac with the specs mentioned below and I just recently moved it to the Mac Mini, both to try to isolate the issue and to have a dedicated media server.
The Mac Mini is headless and runs JRiver in server mode. It is accessed from VLC via Apple TV (this is usually stable), or, for library maintenance, from another Mac device, using screen sharing. Devices include an iMac with the following specs:
Model Name: iMac
Model Identifier: iMac11,1
Processor Name: Intel Core i5
Processor Speed: 2.66 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Processor Interconnect Speed: 4.8 GT/s
Boot ROM Version: 60.0.0.0.0
SMC Version (system): 1.54f36
and also a MacBook Air with the following specs:
Model Name: MacBook Air
Model Identifier: MacBookAir4,1
Processor Name: Intel Core i5
Processor Speed: 1.6 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 4 GB
Boot ROM Version: 130.0.0.0.0
SMC Version (system): 1.74f4
-
Are you saying that you are running MC in server mode (using the command line option)?
-
No, I used the wrong language earlier: I meant that I am running MC with the GUI, but the that the library is being shared on the network via DLNA.
-
Here's another crash log. This one happened while being accessed from VLC on the network, no media actually playing, just attempting to connect and browse the library from a client machine. Same setup as before.
-
Another crash log, same issue. I finally wrote a launchd service to keep JRiver alive as a workaround. At this point my hypothesis is that something in my library is the issue, or others would be reporting this problem more.
I am a developer and have no end of patience in troubleshooting. If someone on the JRiver dev team could suggest what might be the problem in the library and how to begin isolating, I am eager to eliminate this issue.
-
Enabling JRiver logging might help here. If it's a bad file, that bad file normally shows up as being access *right* before the log terminates.
MC logging is a little weird though. After a crash, when you restart MC, the log with the crash will be called "Previous Log". That's the one you want. Turn on logging. Wait for a crash. Fire MC back up and collect logs. Then look at the log file and/or post it here.
Good luck.
PS: I am not a JRiver employee. Just responding because I've seen crashes before.
Brian.
-
Another crash log, same issue. I finally wrote a launchd service to keep JRiver alive as a workaround. At this point my hypothesis is that something in my library is the issue, or others would be reporting this problem more.
I am a developer and have no end of patience in troubleshooting. If someone on the JRiver dev team could suggest what might be the problem in the library and how to begin isolating, I am eager to eliminate this issue.
As Brian said, a log AND crash report from the same incident would be good.
The last one crashed in a UDP network call.
Also, could you post the info from the MC25 crash instead of MC23, the changes in code since then make it more difficult to track down the issue. Thanks.
-
The log has been running since the beginning of the installation and the log is now over 212MB. Attachments are max 1200K. Anyplace I can upload it to the developers privately?
-
Also I have the trial of v25. Glad to start running that if it will help, but I want to get this solved before I pay for another license. I tried rolling back to troubleshoot, but the crash is happening on all the versions mentioned above.
-
The wiki has a topic on Logging. Upload to Dropbox or similar.
-
The log has been running since the beginning of the installation and the log is now over 212MB. Attachments are max 1200K. Anyplace I can upload it to the developers privately?
Both MC24 and MC25 have options to truncate and restart the log.
If the Log is 212MB though it can't be crashing very much since the logs are rotated automatically on restart...
-
Not sure how to answer that. It has crashed at least as many times as I've posted logs for.
Here's the 212MB log file I mentioned in a .ZIP file.
https://drive.google.com/open?id=1PmcGQU2mIzfaHpwtzGn1XL9lFTad9acD
-
Here's both a MC and OSX log from the latest crash.
https://drive.google.com/open?id=1RBoxfFmLRy87H8ddIlA8cMrHTAirPfvo
https://drive.google.com/open?id=1Acvu5TQN0EIOFOn8jGYWSWRmkVinnyWz
-
I really can't debug this without a MC25 crash log/dump.
-
I really can't debug this without a MC25 crash log/dump.
Here's an OSX and MC log from a crash on MC25.
https://drive.google.com/open?id=1Xi-gKtkrBYe25eG_Z1a5oxPXO0u2MbY5
-
And another
https://drive.google.com/open?id=1OCOUhFvpALbNn9WqsJHZXK3BHubU8nby
-
Please give the latest build, 25.0.50 a try. Thanks!
-
My trial extension has expired. If you want to send me another extension I'll keep sending logs.
-
We can't extend it a second time. You could try on another machine if you have one.
-
If you read the thread you'll see this is already the second machine tried.
I'm going to consider the question answered. I first reported it over a month ago, when there was plenty of time left in the MC25 trial to offer troubleshooting steps. Also the build 25.0.50 suggested by bob was just released today.
Pretty fishy, guys.
-
I don't read every thread every time. Sorry.
Fishy?
-
correct.