Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[planet]

Recently upgraded from Win7 to Win8.1, and installed the OS from scratch.

Running 1.0.138 on the stable channel.

When the app initially loads, I can quit it without a problem.  However, if I ever view music or start using the app in any typical way, and then attempt to quit out, the app hangs (with a spinning blue ring and a "Not responding" indicator on the task manager).  This is perfectly reproducible.

I've also noticed the app is consuming 15-60% of CPU on a regular basis -- and continues to do so when it's not responsive, before I end the task.

Any thoughts on what I could try, or get debug data to the team?

[adamt]

Are you using Media Network?  If so, for troubleshooting you could try disabling it and seeing if the problem persists. 

[planet]

Nope, not using Media Network.  I'm baffled.

[glynor]

I've had this before with Audio Setup problems:
http://wiki.jriver.com/index.php/Audio_Troubleshooting_Guide

In particular, I've seen this when using the wrong WASAPI setting (default vs. push).  You may also want to check your audio device driver (you aren't just using the ones Windows auto-detected when it installed, right?).

[planet]

I've had this before with Audio Setup problems:
http://wiki.jriver.com/index.php/Audio_Troubleshooting_Guide

In particular, I've seen this when using the wrong WASAPI setting (default vs. push).  You may also want to check your audio device driver (you aren't just using the ones Windows auto-detected when it installed, right?).

Thanks.  Tried a few more things:
- disabled all DSP effects
- installed different versions of all audio drivers
- tried different audio devices and output modes

All with the same effect: hangs when I try to quit, i.e.: click File -> Exit (or click the X window widget or hit Alt-F4), get blue-spinning-circle, then let Windows ask me to kill it (or end the process directly via Task Manager).

The troubleshooting guide suggested posting the log zip file.  Attached.

[glynor]

- installed different versions of all audio drivers
- tried different audio devices and output modes

More information please.

If it isn't audio drivers or setup (which could conceivably be that one of your audio devices is broken under Windows 8 by the way), it is probably Anti-Virus, based on your description of the symptoms.  To be clear, MC is developed on Windows 8.1, and many people run it (including me).  This is not a Windows 8.1 thing.  If it worked before on the same system, and doesn't now, then something has changed on your computer.

But, I can't help with that kind of detail. Sorry.  What, specifically, did you try?

Also, you should try all of the stuff in the general troubleshooting guide, or explain what has been done, at least.

[glynor]

Looking at the log, I see this near the end:

Code: [Select]

0028765: 4752: General: CMainUIWnd::Resize: Finish (78 ms)
0028765: 4752: General: CMainUIWnd::SetMCView: View show / update time: 76.260
0028765: 4752: General: CMainUIWnd::SetMCView: Finish (328 ms)
0028859: 4752: General: JRWebWnd::OnTerminate: Start
0028859: 4752: General: JRWebWnd::OnTerminate: Sending destroy command
0028859: 4752: General: JRWebWnd::OnTerminate: Stopping process
0028656: 2996: General: JRWebApp::Destroy: Start
0028656: 2996: General: JRWebApp::Destroy: Finish (0 ms)
0028656: 2996: General: JRWebApp::Run: Finish (28640 ms)
0028656: 2996: General: JRWebApp::ExitInstance: Start
0028656: 2996: General: JRWebApp::ExitInstance: Stopping web engine
0028781: 2996: General: JRWebApp::ExitInstance: Stopping callback server
0028781: 2996: General: JRWebApp::ExitInstance: Stopping interface server
0028781: 2996: General: JRIpcServerThreaded::ServerStop: Start
0028781: 2996: General: JRIpcServerThreaded::ServerStop: Canceling thread
0028781: 2996: General: JRIpcServerThreaded::ServerStop: Canceling pending run
0028781: 2996: General: JRIpcServerThreaded::ServerStop: Stopping thread
0028781: 3688: General: JRIpcServerThreaded::Thread: Thread finishing (cancel: 1; errors: 1)
0028781: 3688: General: JRIpcServerThreaded::Thread: Finish (28781 ms)
0028812: 2996: General: JRIpcServerThreaded::ServerStop: Canceling response threads
0028812: 2996: General: JRIpcServerThreaded::ServerStop: Deleting response threads
0028812: 2996: General: JRIpcServerThreaded::ServerStop: Closing notification window
0028812: 2996: General: JRIpcServerThreaded::ServerStop: Finish (31 ms)
0028812: 2996: General: JRWebApp::ExitInstance: Finishing
0029031: 4752: General: JRWebWnd::OnTerminate: Closing callback server
0029031: 4752: General: JRIpcServerThreaded::ServerStop: Start
0029031: 4752: General: JRIpcServerThreaded::ServerStop: Canceling thread
0029031: 4752: General: JRIpcServerThreaded::ServerStop: Canceling pending run
0029031: 4752: General: JRIpcServerThreaded::ServerStop: Stopping thread
0029031: 4276: General: JRIpcServerThreaded::Thread: Thread finishing (cancel: 1; errors: 1)
0029031: 4276: General: JRIpcServerThreaded::Thread: Finish (28875 ms)
0029047: 4752: General: JRIpcServerThreaded::ServerStop: Canceling response threads
0029047: 4752: General: JRIpcServerThreaded::ServerStop: Deleting response threads
0029047: 4752: General: JRIpcServerThreaded::ServerStop: Closing notification window
0029047: 4752: General: JRIpcServerThreaded::ServerStop: Finish (16 ms)
0029047: 4752: General: JRWebWnd::OnTerminate: Closing window
0029047: 4752: General: JRWebWnd::OnTerminate: Finish (188 ms)
0029625: 3804: Playback: CWaveBinFilter::CheckMediaType: Format: 48kHz 32bit 26ch
0029640: 4228: Playback: CDXWaveFeeder::OnGraphNotify: Start: Thread: 0x1084, Graph: 0x1318058
0029640: 4228: Playback: CDXWaveFeeder::OnGraphNotify: Event 34816 param1 0, Param2 -1868223061
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 48kHz 32bit 26ch
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0030156: 4228: Playback: CWaveOutBin::DestroyBin: Start
0030156: 4228: Playback: CWaveOutBin::DestroyBin: Canceling play thread
0030156: 4228: Playback: CWaveOutBin::DestroyBin: Deleting play thread
0030156: 4228: Playback: CWaveOutBinPlayThread::~CWaveOutBinPlayThread: Start
0030156: 4168: Playback: CWaveOutBinPlayThread::Thread: Finish (1516 ms)
0030172: 4228: Playback: CWaveOutBinPlayThread::~CWaveOutBinPlayThread: Finish (16 ms)
0030172: 4228: Playback: CWaveOutBin::DestroyBin: Deleting objects
0030172: 4228: Playback: CWaveOutBin::DestroyBin: Finish (16 ms)
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 44.1kHz 64bit 2ch
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0030172: 4228: Playback: CWaveOutBin::CreateBin: Start
0030172: 4228: Playback: CWaveOutBin::DestroyBin: Start
0030172: 4228: Playback: CWaveOutBin::DestroyBin: Finish (0 ms)
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 48kHz 32bit 26ch
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 44.1kHz 64bit 2ch
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0030172: 4228: Playback: CWaveOutBin::CreateBin: Finish (0 ms)
0030172: 4228: Playback: CDXWaveFeeder::OnGraphNotify: End: Thread: 0x1084, Graph: 0x1318058, 532ms
0030172: 3480: Playback: CWaveOutBinPlayThread::Thread: Start
0030500: 4752: General: CMCUICore::SystemPowerManager_UpdateActions: Start
0030500: 4752: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
0030500: 4752: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
0031078: 4752: General: CMCToolsCore::StopTools: Start
0031078: 4752: General: CMCToolsCore::StopTools: Stopping tools
0031078: 4752: General: CMCToolsCore::StopTools: Stopping loader thread
I think this is where you asked it to close:

Code: [Select]

0028859: 4752: General: JRWebWnd::OnTerminate: Start
0028859: 4752: General: JRWebWnd::OnTerminate: Sending destroy command
0028859: 4752: General: JRWebWnd::OnTerminate: Stopping process
Then, JRWebWnd took a while to finish something:

Code: [Select]

0028656: 2996: General: JRWebApp::Run: Finish (28640 ms)
0028656: 2996: General: JRWebApp::ExitInstance: Start
0028656: 2996: General: JRWebApp::ExitInstance: Stopping web engine
0028781: 2996: General: JRWebApp::ExitInstance: Stopping callback server
0028781: 2996: General: JRWebApp::ExitInstance: Stopping interface server
That's not crazy, though it did take quite a bit longer on your system than on mine.  Here's mine from a test I just did:

Code: [Select]

0018391: 5324: General: JRWebApp::Run: Finish (18312 ms)
0018391: 5324: General: JRWebApp::ExitInstance: Start
0018391: 5324: General: JRWebApp::ExitInstance: Stopping web engine
0018438: 5324: General: JRWebApp::ExitInstance: Stopping callback server
0018438: 5324: General: JRWebApp::ExitInstance: Stopping interface server
And then, again, here:

Code: [Select]

0028781: 3688: General: JRIpcServerThreaded::Thread: Finish (28781 ms)
You have quite a bit higher latency than mine:

Code: [Select]

0018438: 5316: General: JRIpcServerThreaded::Thread: Finish (18375 ms)
But, either way, other than that your system seems to be doing everything way slower than mine (which, I don't think, should be dramatically the case, based on our respective system specs) the logs match, up until here:

Code: [Select]

0029047: 4752: General: JRWebWnd::OnTerminate: Closing window
0029047: 4752: General: JRWebWnd::OnTerminate: Finish (188 ms)
0029625: 3804: Playback: CWaveBinFilter::CheckMediaType: Format: 48kHz 32bit 26ch
0029640: 4228: Playback: CDXWaveFeeder::OnGraphNotify: Start: Thread: 0x1084, Graph: 0x1318058
0029640: 4228: Playback: CDXWaveFeeder::OnGraphNotify: Event 34816 param1 0, Param2 -1868223061
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 48kHz 32bit 26ch
0029640: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0030156: 4228: Playback: CWaveOutBin::DestroyBin: Start
0030156: 4228: Playback: CWaveOutBin::DestroyBin: Canceling play thread
0030156: 4228: Playback: CWaveOutBin::DestroyBin: Deleting play thread
0030156: 4228: Playback: CWaveOutBinPlayThread::~CWaveOutBinPlayThread: Start
0030156: 4168: Playback: CWaveOutBinPlayThread::Thread: Finish (1516 ms)
0030172: 4228: Playback: CWaveOutBinPlayThread::~CWaveOutBinPlayThread: Finish (16 ms)
0030172: 4228: Playback: CWaveOutBin::DestroyBin: Deleting objects
0030172: 4228: Playback: CWaveOutBin::DestroyBin: Finish (16 ms)
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using specified output format
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 44.1kHz 64bit 2ch
0030172: 4228: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
That same thing, then, seems to just keep looping and looping.  As I suggested before, it looks like an audio device issue.  I have none of that in the same section of my shutdown.  Here's mine:

Code: [Select]

0019000: 5328: General: JRWebWnd::OnTerminate: Closing window
0019000: 5328: General: JRWebWnd::OnTerminate: Finish (110 ms)
0019000: 5328: General: CMCShutdownHelper::Cleanup: Destroying main UI helper
0019000: 5328: General: CMCMainUIHelper::Destroy: Start
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying action windows
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying menu bars
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying player
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying borders
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying status bar
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying tree
0019000: 5328: General: CMCMainUIHelper::Destroy: Destroying playback display
0019000: 5328: General: CMCMainUIHelper::Destroy: Finish (0 ms)
0019000: 5328: General: CMCShutdownHelper::Cleanup: Running shutdown settings
0019000: 5328: TV: CTVTunerHelper::CleanupPrograms: Start
0019000: 5328: Database: CDataHolder::Load: Field: Recording Rule ID; Files: 136562; Pointer bytes: 0; Data bytes: 48; Elapsed ms: 0.169
0019000: 5328: Database: CSearchFilesHelper::GetResults: Search: [Media Type]=[Video] [=TVInfo(IsRecordedProgram)]=[1]; Elapsed ms: 10.124
0019000: 5328: TV: CTVTunerHelper::CleanupPrograms: Checking 0 recorded programs for deletion
0019000: 5328: TV: CTVTunerHelper::CleanupPrograms: 0 recordings found to have episode based deletion attribute
0019000: 5328: TV: CTVTunerHelper::CleanupPrograms: Found 0 programs to delete
0019000: 5328: TV: CTVTunerHelper::CleanupPrograms: Finish (0 ms)
0019000: 5328: General: CMCShutdownHelper::Cleanup: Shutting down tools
Same two initial lines, but then in your log, that's the last thing I can see where yours is even trying to shut down anymore.  It looks like it is stuck iterating over the Audio Device Output, for some reason.

[glynor]

The way higher task finishing times makes me think: Anti-Virus.
The looping audio device thing makes me think: locked up audio device driver, and MC can't release its handle for the device.

[planet]

The problem is solved.  I actually noticed that JRiver was also chewing up 80% of my system's CPU.  That's 80% on an 8-core i7 4770k system with 32G of RAM.   This lead me via Google to disabling the Spectrum Analyzer -- which helped eliminate the load on most of the cores, but it was still pinning 2.  Ultimately, this lead me to disable auto-import.  Et voila -- CPU load dropped to near zero, and the app quits without hanging.

(I figure this is a problem because the size of my library is so large, 57k files and over 800G -- but I'm not sure.)

Anyway, happy again.  No need to flee to Foobar. 

[glynor]

No, that's actually a reasonably small Library by some of our standards here (my main Library is around 12TB right now).  And Auto-Import doesn't regularly scan folders (except once every two hours).  It works differently and only responds to actual newly created files.  Let's ignore that one for now, though.

The Spectrum Analyzer problem points to general system instability.  I'm guessing a Video Card driver, though it could be a range of things.  That's basically... Math.  Your computer isn't doing math right, which isn't good, or perhaps just can't draw it on the screen right.

Have you done a general stability test like Prime95 on that bad boy?  How about DirectX Diag?

[planet]

No, that's actually a reasonably small Library by some of our standards here (my main Library is around 12TB right now).  And Auto-Import doesn't regularly scan folders (except once every two hours).  It works differently and only responds to actual newly created files.  Let's ignore that one for now, though.

The Spectrum Analyzer problem points to general system instability.  I'm guessing a Video Card driver, though it could be a range of things.  That's basically... Math.  Your computer isn't doing math right, which isn't good, or perhaps just can't draw it on the screen right.

Have you done a general stability test like Prime95 on that bad boy?  How about DirectX Diag?

Thanks for the continued assist.  Yeah, I've run some stability tests, including both of those.  Re-running...

(1) dxdiag still reports no problems on all tabs, and I'm getting very good framerates on lots of games.  (I do have a new LG 21:9 display, 3440x1440, but I've had no problems with it, and would not expect that to be the issue.)  I'm running Nvidia 337.88 WHQL drivers.
(2) Prime95 continues to run fine, too, passing tests.

I wish I had other evidence that there was a problem.  Other than JRiver (before deactivating spectrum analyzers and auto-import), everything seems fine.  Hmm.  Any other diagnostic ideas?

[glynor]

Are you running any skinning engines, Desktop enhancers, or things remotely like StarDock's WindowBlinds?

[planet]

Are you running any skinning engines, Desktop enhancers, or things remotely like StarDock's WindowBlinds?

No on all counts.  Relatively vanilla.

[Frobozz]

Anything like a screen sharing or remote access application or VM environment installed?  Some apps like that may mess with graphics in an effort to accelerate remote screens.

For the auto-import problems do you have MC monitoring a directory that something like Google Drive sync or some other sync tool is also monitoring?

Just a couple stabs in the dark

[glynor]

Anything like a screen sharing or remote access application or VM environment installed?  Some apps like that may mess with graphics in an effort to accelerate remote screens.

For the auto-import problems do you have MC monitoring a directory that something like Google Drive sync or some other sync tool is also monitoring?

Just a couple stabs in the dark

Decent guesses.  The mirror driver thing is certainly possible.  Though, I can confirm that MC runs fine alongside vmware Workstation 10, vmware Fusion, and Parallels Desktop 9.  I'm also pretty sure they use VirtualBox bottles when developing MC, so that should be pretty well tested too.  I think I have the mirror driver for TightVNC installed too, but I pull that off sometimes (because it is incompatible with something-or-other) so I'm not 100% sure on that.

And, incidentally, I use DisplayFusion on all of my machines and have no problems with it and MC (it and vmware Workstation, however, is another story).

Also, another dark-stab, is your media on an external drive like a USB disk or NAS?

Also, I haven't seen you respond to any of the stuff I've said about Anti-Virus.  MC does NOT like AV applications messing with its access to its own Library files.  Your log shows latencies much higher than mine for essentially all operations, and our machines are not that different.  I think that's either disk or AV software being dumb.

[Pinch]

I've had precisely the same problem. Solved by uninstalling a large number of unrecognised Windows TAP adapters.

See the last post here: http://yabb.jriver.com/interact/index.php?topic=89852.0

Hope this helps!