Topic: "Media Center Closed Unexpectedly" v25 (Read 24044 times)

mwheelerk · « **on:** December 08, 2015, 08:21:58 am »

Since upgrading to version 25 each time I go to close Media Center I am getting the "Media Center Closed Unexpectedly" notice on my MacBook. I stop what is playing. Go to Media Center on the toolbar and select quit then the message pops up. Anyone else experiencing this. Anything I should do or can do to stop this. It is not crashing while I am using it (which is usually when you see that message) but only when I initiate Quit.

blgentry · « **Reply #1 on:** December 08, 2015, 08:43:01 am »

I'm not seeing this here with MC21.0.25, and OSX 10.9.5 . I rarely quit MC though. I leave it running 99% of the time. I also don't quit apps from the Dock. I usually quit apps with Command-q or the app's main menu Quit item. It's probably the same thing, but I wanted to mention it.

Do you have MC installed in the Applications folder? Or are you running it from the DMG? It should be installed in Applications, but a lot of people mistakenly run it from the DMG.

Brian.

Radio Seaside · « **Reply #2 on:** December 08, 2015, 09:37:40 am »

I experienced the same, download jriver v25, put it in applications. When I quit it crashed. Normally it is always on. But I wanted to make a pc restart. So I went back to v24. That doesn't crash Macbook pro - OS X 10.11.1

mwheelerk · « **Reply #3 on:** December 08, 2015, 07:29:04 pm »

It continues to exhibit this behavior not with every closing but frequently. I have installed this version of JRiver as I have every version prior without this issue.

mwheelerk · « **Reply #4 on:** December 08, 2015, 10:16:36 pm »

I tried a fresh download and clean new install but the same issue persists. Beyond the annoying unexpected quit notice it seems to be functioning properly.

mwheelerk · « **Reply #5 on:** December 09, 2015, 07:17:37 am »

The error message of "Media Center Quit Unexpectedly" continue to come up when I close even after my fresh install. Later today I will reinstall .24 to see if that eliminates the problem.

mwheelerk · « **Reply #6 on:** December 09, 2015, 08:12:51 am »

I don't know if this might help you keys identify the issue or not. Just some added information. I don't generally shut my computer off but put it to sleep. This occurs though at anytime I'm using JRiver .25. Here is part of the error message I see.

"Process: Media Center 21 [2468]
Path: /Applications/Media Center 21.app/Contents/MacOS/Media Center 21
Identifier: com.jriver.MediaCenter21
Version: 21.0.25 (?)
Code Type: X86-64 (Native)
Parent Process: ? [1]
Responsible: Media Center 21 [2468]
User ID: 501

Date/Time: 2015-12-09 07:08:45.590 -0700
OS Version: Mac OS X 10.11.2 (15C50)
Report Version: 11
Anonymous UUID: 003CA111-DA88-2BA9-CBF1-5D58CE1B67EC"

Radio Seaside · « **Reply #7 on:** December 09, 2015, 01:46:57 pm »

This is a part of my crash report, tried v25 this evening one more time, now back to v24 again.

Process: Media Center 21 [378]
Path: /Applications/Media Center 21.app/Contents/MacOS/Media Center 21
Identifier: com.jriver.MediaCenter21
Version: 21.0.25 (?)
Code Type: X86-64 (Native)
Parent Process: ? [1]
Responsible: Media Center 21 [378]
User ID: 501

Date/Time: 2015-12-09 20:41:04.085 +0100
OS Version: Mac OS X 10.11.2 (15C50)
Report Version: 11
Anonymous UUID: 83E3A2A3-BDB3-2EE1-D77A-1EA4D5AEA9E6

Time Awake Since Boot: 190 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000010f4294a6
Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0x10f4294a6:
__LINKEDIT 000000010f1ce000-000000010f338000 [ 1448K] r--/rwx SM=COW /Applications/Media Center 21.app/Contents/MacOS/libJRImage.dylib
--> Process Corpse Info 000000010f338000-000000010f538000 [ 2048K] rw-/rwx SM=COW
__TEXT 000000010f5fa000-000000010f7e6000 [ 1968K] r-x/rwx SM=COW /Applications/Media Center 21.app/Contents/MacOS/libJRDisc.dylib

Application Specific Information:
Performing @selector(terminate:) from sender NSMenuItem 0x10db7adf0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ?     0x000000010f4294a6 0 + 4550988966
1 ?     0x000000010f42addc 0 + 4550995420
2 ?     0x000000010f42a3a5 0 + 4550992805
3 ?     0x000000010f42a28d 0 + 4550992525
4 libsystem_c.dylib     0x00007fff9072a46b __cxa_finalize_ranges + 345
5 libsystem_c.dylib     0x00007fff9072a76f exit + 55
6 com.jriver.MediaCenter21    0x000000010055e695 JRProcess::TerminateCurrentProcess(unsigned int) + 9
7 com.jriver.MediaCenter21    0x0000000100ab87f5 CMCShutdownHelper::Cleanup(JRString const&, bool, CSystemShutdown::EShutdownModes) + 1973
8 com.jriver.MediaCenter21    0x0000000100999054 CMainFrame::Close(bool) + 422
9 com.jriver.MediaCenter21    0x0000000100a93f41 CMCPlayerApp::StopRun() + 837
10 com.jriver.MediaCenter21    0x00000001004bb673 -[JRAppDelegate applicationShouldTerminate:] + 20
11 com.apple.AppKit    0x00007fff9234be33 -[NSApplication _docController:shouldTerminate:] + 69
12 com.apple.AppKit    0x00007fff9234bcd0 __91-[NSDocumentController(NSInternal) _closeAllDocumentsWithDelegate:shouldTerminateSelector:]_block_invoke + 534
13 com.apple.AppKit    0x00007fff9234b8e7 -[NSDocumentController(NSInternal) _closeAllDocumentsWithDelegate:shouldTerminateSelector:] + 1309
14 com.apple.AppKit    0x00007fff9234b3a3 -[NSDocumentController(NSInternal) __closeAllDocumentsWithDelegate:shouldTerminateSelector:] + 291
15 com.apple.AppKit    0x00007fff9234b074 -[NSApplication _shouldTerminate] + 705
16 com.apple.AppKit    0x00007fff9234a566 -[NSApplication terminate:] + 762
17 libsystem_trace.dylib     0x00007fff906ab07a _os_activity_initiate + 75
18 com.apple.AppKit    0x00007fff9222d51d -[NSApplication sendAction:to:from:] + 460
19 com.apple.AppKit    0x00007fff9222d2b7 -[NSMenuItem _corePerformAction] + 336
20 com.apple.AppKit    0x00007fff9222d017 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114
21 libsystem_trace.dylib     0x00007fff906ab07a _os_activity_initiate + 75
22 com.apple.AppKit    0x00007fff922ed1f0 -[NSMenu performActionForItemAtIndex:] + 131
23 com.apple.AppKit    0x00007fff922ed163 -[NSMenu _internalPerformActionForItemAtIndex:] + 35
24 com.apple.AppKit    0x00007fff922ecfbb -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 107
25 com.apple.AppKit    0x00007fff92215ea1 NSSLMMenuEventHandler + 708
26 com.apple.HIToolbox     0x00007fff97ef07be Dispatc

JimH · « **Reply #8 on:** December 09, 2015, 02:01:19 pm »

Quote from: Radio Seaside on December 09, 2015, 01:46:57 pm

This is a part of my crash report, tried v25 this evening one more time, now back to v24 again.

That would be build 25, not version 25.

mwheelerk · « **Reply #9 on:** December 10, 2015, 06:44:28 am »

I have gone back to build 24 and the error message has stopped so there would appear to be an issue of some sort with build 25

JohnT · « **Reply #10 on:** December 10, 2015, 09:21:15 am »

Do you have any tips for trying to replicate the problem? I have a Mac Mini and a MacBook Pro running El Capitan 10.11.2 and haven't been able to reproduce it.

1. Are you playing music at the time of shutdown? If so, are they local or networked and what file format?
2. How do you close MC? Using Cmd-Q or menu or clicking the little red close button at the upper left corner of the app?
3. Does it only happen after MC has been running for a long time? If you start it up now, leave it running for a minute or two and then close, does it crash every time?

Could you send a Media Center log plus a Mac crash report after a crash on close sequence? Thanks.

Radio Seaside · « **Reply #11 on:** December 10, 2015, 09:38:06 am »

John T,
It happens after music has been played and stopped , if you open and quit without playing music there is no software crash Music Flac / mp3 Close with quit botton under mediacenter 21, Programme has not been running for a long time, I found out after updating it early in the morning, just beforwe going to work. Played a snip of a song and closed the programme. So even when I play say 30 seconds of a song it already happens.
crashreport included (pdf) Macbook and mediacenter 21.0.25

JimH · « **Reply #12 on:** December 10, 2015, 09:39:29 am »

Any type of file? MP3? FLAC?

mwheelerk · « **Reply #13 on:** December 10, 2015, 03:50:50 pm »

My library is all AIFF. I am generally playing from smart list with auto shuffle but do play album titles only. My procedure is to hit the stop play. Most times I refresh the smart list as usually I have a number of plays or date trigger to eliminate songs from that list. I close by going to the top of my MacBook selecting Media Center and Quit. Media Center closes in what appears to be normal but within 1 or 2 seconds the error report appears about "Media Center Closed Unexpectedly".

I'm back on build 24 and in three sessions were I followed above no error report has appeared.

JimH · « **Reply #14 on:** December 10, 2015, 05:49:05 pm »

Thanks for the details.

JohnT · « **Reply #15 on:** December 11, 2015, 08:15:55 am »

Quote from: Radio Seaside on December 10, 2015, 09:38:06 am

John T,
It happens after music has been played and stopped , if you open and quit without playing music there is no software crash Music Flac / mp3 Close with quit botton under mediacenter 21, Programme has not been running for a long time, I found out after updating it early in the morning, just beforwe going to work. Played a snip of a song and closed the programme. So even when I play say 30 seconds of a song it already happens.
crashreport included (pdf) Macbook and mediacenter 21.0.25

The log you sent doesn't show a shutdown process occurring. I think it may be "Log.txt" rather the "Previous Log.txt" that we need to analyze the crash from the previous run of the program. Could you try again to provide a log file by letting MC crash, then restarting and selecting Help / Logging / Report problem.. This produces a zip file on your desktop that you can attach here. Thanks!

I can't reproduce it. One possibility is there is a socket reading thread that is stuck when the program tries to exit, which could cause a crash. You might be able to prove/disprove this by turning off your media networking, restarting MC, and then see if the problem still exists. Still, the log file mentioned above might be very helpful.

Radio Seaside · « **Reply #16 on:** December 11, 2015, 02:37:53 pm »

John T, zipfile crash after quitting mediacenter.
Hope it will help,

One possibility is there is a socket reading thread that is stuck when the program tries to exit, which could cause a crash. You might be able to prove/disprove this by turning off your media networking, restarting MC, and then see if the problem still exists

Put out the ethernet cable and mediacenter didn't crash, when I put it back and quit mediacenter it crashed.
Build 24 works fine. Never had this issue with any of the builds.

Ronald

mwheelerk · « **Reply #17 on:** December 16, 2015, 07:26:39 pm »

I'm going to do a fresh download and install of build 25 and see if the problem continues. I haven't had an issue since reinstalling build 24.

Short and sweet. I played two songs, shut down Media Center as described above and the error report popped up immediately. Very strange. I mean it plays fine. I don't notice an issue other than the irritation of the report popping up.

mwheelerk · « **Reply #18 on:** December 23, 2015, 09:36:22 pm »

I've stayed on build 24 without issue. Only two of us apparently have experience this. I guess I'll just wait for the next build and see what happens then.

Radio Seaside · « **Reply #19 on:** December 24, 2015, 01:17:06 pm »

So do I.

Ronald

JohnT · « **Reply #20 on:** December 30, 2015, 04:45:24 pm »

Please try the latest build 21.0.31 and let us know if it fixes the crash issue. Thanks.

mwheelerk · « **Reply #21 on:** December 30, 2015, 09:11:13 pm »

Quote from: JohnT on December 30, 2015, 04:45:24 pm

Please try the latest build 21.0.31 and let us know if it fixes the crash issue. Thanks.

I just downloaded build 21.0.31. I have been on 21.0.24 for quite some time now without the log crash report after closing. The first time I closed 21.0.31 I got the "Closed Unexpectedly" report on my Macbook.

Radio Seaside · « **Reply #22 on:** December 31, 2015, 03:45:07 am »

Same overhere, installed build 31, closed it and it crashed. The same as with build 25.

chriswimlett · « **Reply #23 on:** January 01, 2016, 10:59:50 am »

I'm still getting "quit unexpectedly" crashes with build 31. It seems linked to playback. I've recently been doing a lot of metadata editing in MC, without playing any tracks, and I'm pretty sure it has not crashed on quit in this situation. I'm running OS X 10.11.2.

mwheelerk · « **Reply #24 on:** January 02, 2016, 11:33:36 am »

It may be linked to playback. Each time this has happened has been after a period of playback. This morning I had JRiver open without playing and when I went to close it a few minutes later I did not receive the error message.

Just to be clear, what I am getting is a "Closed Unexpectedly" message after trying to close JRiver. I am not receiving a "Quit Unexpectedly" message which is generally indicative of a crash during playback. This occurs after playback and in the act of closing JRiver.

whatlarks · « **Reply #25 on:** January 11, 2016, 06:06:11 am »

Having just upgraded to the Master Licence and installed MC21 on my MacBook Pro (OSX 10.8.5), I am also experiencing this problem. My error message is definitely, 'Quit Unexpectedly' (not Close) whilst closing down MC (currently build 31). This happens every-time I close down MC, irrespective of whether I have just played an audio or video file. I have attached a copy of the zipped log files.

In case this is relevant, my MacBook Pro is set up to use the library from the MC server on my Windows based PC (running the MC 21.0.23) via my local network. All audio and video files are stored on an external hard disk connected to this PC.

Thanks,
Ian

mwheelerk · « **Reply #26 on:** January 15, 2016, 12:33:47 am »

I have no idea what would have changed or why. I've done nothing different with my library since upgrading to .31. The problem had continued as it had since .25, until today. I've opened and closed the library four times today. The error message had not appeared. It previously happened overtime I closed JRiver. If anything changes I'll let you know.

chriswimlett · « **Reply #27 on:** January 15, 2016, 09:25:56 am »

I'm continuing to get 'Quit Unexpectedly' every time I quit MC 21 (build 31) after playback. As an experiment I tried disabling 'Use Media Network to share this library and enable DLNA' before quitting, but MC still crashed. I don't think it's ever crashed when I've just been using MC to edit metadata.

Where are the log files stored on a Mac?

blgentry · « **Reply #28 on:** January 15, 2016, 09:33:16 am »

^ MC doesn't generate log files by default. You can enable that option though:

http://wiki.jriver.com/index.php/Logging

A crash makes a crash dump, which is shown on screen and can be printed copied for later analysis. In general some things are logged to the system log on a Mac, but usually not anything that's super duper useful that's application specific. It's more like informational messages and also real system level stuff like "error reading rdisk03". You can get to the system logs with Applications > Utilities > Console .

Brian.

chriswimlett · « **Reply #29 on:** January 16, 2016, 05:29:02 am »

Thanks Brian. I've attached a log file which covers one of the crashes and also a crash dump. Is it enough to attach these here?

Chris

blgentry · « **Reply #30 on:** January 16, 2016, 09:52:52 am »

^ Those might help the developers trace the issue. I looked through both documents and nothing jumped out at me as being an issue. But I don't work for JRiver and I don't know their code. I'm not even all that good at analyzing their log files.

Maybe someone else can read them and figure something out.

Brian.

chriswimlett · « **Reply #31 on:** January 16, 2016, 10:44:37 am »

Thanks Brian - I must say the log didn't make much sense. It's not a big deal as I tend to leave JRiver running all day and just shut down in the evening. It's just a bit untidy given JRiver's usual reliability.

Chris

mwheelerk · « **Reply #32 on:** January 17, 2016, 12:06:03 pm »

I'm 3 days later now since my issue suddenly disappeared. I have no explanation as to why but I have not had an incident of the "Closed Unexpectedly" in those 3 days over repeated openings and closings of JRiver. I guess there nothing else for me to post in this thread as the issue that lasted almost six weeks since the intro of build 25 is for all intents and purposes gone for me.

I did check to see if there was some background update for Mac OS in this timeframe but there were none.

Radio Seaside · « **Reply #33 on:** January 20, 2016, 09:13:51 am »

Here still the same, quit is crash.

Ronald

Radio Seaside · « **Reply #34 on:** February 11, 2016, 08:43:21 am »

New build,0.45, after playing music and quit it still crashes.

chriswimlett · « **Reply #35 on:** February 11, 2016, 09:21:17 am »

Same here. Installed Build 45 but MC still crashes on quit after playback.

Awesome Donkey · « **Reply #36 on:** February 11, 2016, 10:19:04 pm »

For those experiencing the crash issue with build 45, please try these troubleshooting steps here: http://yabb.jriver.com/interact/index.php?topic=103169.msg716396#msg716396

Hopefully we can narrow down the issue to a specific feature or features.

mwheelerk · « **Reply #37 on:** February 12, 2016, 07:46:16 am »

Quote from: Awesome Donkey on February 11, 2016, 10:19:04 pm

For those experiencing the crash issue with build 45, please try these troubleshooting steps here: http://yabb.jriver.com/interact/index.php?topic=103169.msg716396#msg716396

Hopefully we can narrow down the issue to a specific feature or features.

Immediately following upgrade to build 45 the error message at closing returned except now the message I get with 45 is "Quit Unexpectedly" instead of the "Closed Unexpectedly" that I began seeing with 25 and continuing with 31 until January 17th.

Now I'm beginning to suspect something more is going on. I have been experiencing increased incidents of drop out during playback and/or locking up during playback. At times JRiver stutters like a skipping record then will suddenly start and stop songs and then jump forward 3 or 4 songs before continuing to play. I have also had instances of JRiver "losing" my music renderer in the DLNA set up. I had been attributing this to my internet service/wifi but each time I did a diagnostic on those it showed as good.

I suspect an issue related to JRiver beginning with build 25 and continuing with 31 and 45 because last night I reverted to build 24 which is the last build I had no issues with. Both the issues wit the error messages, "closed" and "quit" have disappeared and the drop outs and stuttering and loss of my renderer have to this point disappeared during approximately 5 hours of playback last night and this morning.

I will reinstall build 45 and using the link provided follow the recommended steps and report back my experience later this weekend.

Awesome Donkey · « **Reply #38 on:** February 12, 2016, 10:09:40 am »

Try disabling Media Network first, as that seems to be the cause for other users.

Radio Seaside · « **Reply #39 on:** February 13, 2016, 05:53:42 am »

Hope the developing team can find a solution for this crashing issue. JRiver does play the music through my network, DSD from PS Audio is the heart in my play systeem and bridge 2 the bridge between my pc and DSD Computer goes to a lancom server and the landcom is connected with the bridge. That works flawless.
Build 0.48 has the same crash issue, which I expected, reading the change log.

Ronald

JimH · « **Reply #40 on:** February 13, 2016, 06:35:58 am »

Radio,
Did you try this?

Quote from: Awesome Donkey on February 12, 2016, 10:09:40 am

Try disabling Media Network first, as that seems to be the cause for other users.

Radio Seaside · « **Reply #41 on:** February 13, 2016, 09:45:44 am »

Yes I did, i have written about it a few messages ago. but without my network connection JRiver is worthless for me. I need it to play the music throughout my house mediaplayers and DSD PS audio. It only crashes when I have played music and push the quit button. So I don't quit, only when I have to restart jriver when it will not play the music.

Ronald

JimH · « **Reply #42 on:** February 13, 2016, 09:54:07 am »

The reason that I asked is that it will make it easier for us to duplicate the problem.

mwheelerk · « **Reply #43 on:** February 14, 2016, 07:59:07 pm »

Quote from: Awesome Donkey on February 12, 2016, 10:09:40 am

Try disabling Media Network first, as that seems to be the cause for other users.

If I do that I will lose my playback

JimH · « **Reply #44 on:** February 14, 2016, 09:15:56 pm »

We need to know if it will make a difference.

blgentry · « **Reply #45 on:** February 14, 2016, 09:20:42 pm »

Radio Seattle and Mwheelerk:

Jim isn't suggesting that turning of Media Network is the *solution* to your problem. Rather, he's asking you to help test. If you both test with Media Network off and do not get the same crash, then that's good data JRiver's team can use to try to track down the problem.

Do the test, then turn Media Network back on and keep using MC as you were before.

Brian.

Radio Seaside · « **Reply #46 on:** February 14, 2016, 09:50:08 pm »

Network "off" it does not crash and with network "on" it crashes.

Ronald

JimH · « **Reply #47 on:** February 15, 2016, 06:50:09 am »

Do you have two network interfaces in use? Wireless and wired at the same time, for example.

Anything unusual about your network?

BradATIMA · « **Reply #48 on:** February 15, 2016, 09:57:19 am »

We have been able to reproduce this crash thanks to the information provided. We have a pretty good idea about what is causing the problem. We just need to track it down. It looks like this is only happening with audio played to a DLNA device when there is a format conversion taking place. Hopefully, there will be a fix for this soon.

Radio Seaside · « **Reply #49 on:** February 15, 2016, 10:24:06 am »

I have a 2,4Ghz and 5Ghz network wireless, dualband router, but most is wired. I play my music, most FLAC, wired. PS AUDIO DSD Bridge 2 is the receiving side, inbetween a lancom server 24 channels which connects all the devices. A router is used for connection with the outside world and for wireless part.
I doesn't matter which music format is played. When there is music played it crahes, when there is no music played it doesn't crash. Build 24 is the last one without crashes.

Ronald

INTERACT FORUM

Author Topic: "Media Center Closed Unexpectedly" v25 (Read 24044 times)