INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Long Time Shutdown Response  (Read 5463 times)

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Long Time Shutdown Response
« on: June 24, 2011, 08:58:13 am »

I've been noticing that when I click on the X in my MC that it's taking about 60 seconds or longer for the process to stop.  Why is that?  It used to just simply quit instantly.  This is getting to be very annoying.  Thanx .... d.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: Long Time Shutdown Response
« Reply #1 on: June 24, 2011, 09:09:43 am »

I've been noticing that when I click on the X in my MC that it's taking about 60 seconds or longer for the process to stop.  Why is that?  It used to just simply quit instantly. 
MC has logging under the Help menu.  You could turn it on and then read the (previous) log after a shutdown.  Take a look at the end.

Any third party plug-ins or anything unusual about your setup?
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #2 on: June 24, 2011, 09:19:49 am »

Well - go figure - I've been stopping and starting MC - and I've rebooted my PC and now it seems to be behaving again.  Can't figure this out.  My MC is basically new - about two weeks old - has about 70000 tunes and until today it's been working fine.  Let's put this issue on hold until it starts acting up again.  I checked the log files and there are none - all are empty.  Shall I turn something on to capture any issues?
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: Long Time Shutdown Response
« Reply #3 on: June 24, 2011, 09:21:32 am »

You have to turn logging on.
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #4 on: June 24, 2011, 09:27:17 am »

You mean - check the check box that reads "Output to a Log File?"  BTW - I tried insert a screenshot here in the forum but could not.  Is there a trick to it?  I clicked on the Insert icon but all I get is
Thanx ... d.
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #5 on: June 24, 2011, 09:31:55 am »

And there she goes again - taking a long time to shutdown.  I'm trying to attach the log file but it's too long.  Is there another way to attach it here?


Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: Long Time Shutdown Response
« Reply #6 on: June 24, 2011, 09:38:45 am »

And there she goes again - taking a long time to shutdown.  I'm trying to attach the log file but it's too long.  Is there another way to attach it here?
Try reading the bottom of it in notepad.  Something will have a big number (in milliseconds) next to it.
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #7 on: June 24, 2011, 04:35:22 pm »

Media Center; Version: 16.0.116; Types: 16383
0000000: 3104: General: Starting logging: Date: 6/24/2011 4:33 PM


0000093: 3104: Database: CMediaDatabase::Load: Start
0000093: 3104: Database: CMediaDatabase::Load: Empty
0000093: 3104: Database: CMediaDatabase::Load: Loading library file
0000093: 3104: Database: CMediaFileIOLoad::Load: Loading: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Library\mediafiles.jmd
0000093: 3104: Database: CMediaDatabase::Load: Checking versions
0000093: 3104: Database: CMediaDatabase::Load: Loading fields
0000093: 3104: Database: CMediaDatabase::Load: Loading files
0000109: 3104: Database: CMediaDatabase::Load: Success
0000109: 3104: Database: CMediaDatabase::Load: Upgrading (if necessary)
0000109: 3104: Database: CMediaDatabase::Load: Finish (16 ms)
0000109: 3104: Database: MCDB::GetBSDB: Creating object
0000109: 3104: Database: CMediaFileIOLoad::Load: Loading: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Library\browser.jmd
0000109: 3104: Database: MCDB::GetVSDB: Creating object
0000109: 3104: Database: CMediaFileIOLoad::Load: Loading: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Library\view state (index).jmd
0000109: 3104: Database: CMediaFileIOLoad::Load: Loading: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Library\view state temporary (index).jmd
0000109: 3104: Database: MCDB::Load: Success -- updating after load
0000109: 3104: Database: MCDB::Save: Start
0000109: 3104: Database: MCDB::Save: Saving (bCleanDB: 0, bForce: 0)
0000109: 3104: Database: MCDB::Save: Finish (0 ms)
0000109: 3104: Database: MCDB::Load: Finish (47 ms)
0000109: 3104: General: CMCPlayerApp::InitInstance: Creating main UI
0000327: 3104: General: CMCPlayerApp::InitInstance: Updating and showing UI
0000327: 3104: General: CMCPlayerApp::InitInstance: Updating after database load
0000327: 3104: Database: CDataHolder::Load: Field: Media Type; Files: 63818; Pointer bytes: 65022; Data bytes: 4168; Elapsed ms: 4.746
0000343: 3104: Database: MCDB::GetCPLDB: Creating object (0)
0000343: 3104: Database: CMediaFileIOLoad::Load: Loading: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Library\curplaylist.jmd
0000343: 3104: General: CMCPlayerApp::InitInstance: Processing command line
0000343: 3104: General: CMCPlayerApp::ExecuteCommandLine: Start
0000343: 3104: General: CMCPlayerApp::ExecuteCommandLine: Command Line:
0000343: 3104: General: CMCPlayerApp::ExecuteCommandLine: Finish (0 ms)
0000343: 3104: General: CMCUICore::SetMode: Start
0000343: 3104: General: CMCUICore::SetMode: Setting UI mode: 0
0000343: 3104: General: CSkinnedMainFrame::LoadWindowPlacement: Restored rectangle: 0, -4, 1682, 1032
0000374: 3104: General: CMainUIWnd::Resize: Start
0000405: 3104: General: CMainUIWnd::Resize: Finish (31 ms)
0000421: 3104: General: CMCUICore::SetMode: Finish (78 ms)
0000421: 3104: General: CMCPlayerApp::InitInstance: Showing startup view
0000421: 3104: General: CMainUIWnd::SetMCView: Start
0000421: 3104: General: CMainUIWnd::SetMCView: View info name: Start
0000421: 3104: General: CMainUIWnd::SetMCView: Hiding old view
0000421: 3104: General: CMainUIWnd::SetMCView: Creating new view
0000437: 3104: General: CMCViewContainerWnd::Create: Start
0000437: 3104: General: CMCViewContainerWnd::Create: Creating window
0000437: 3104: General: CMCViewContainerWnd::Create: Initializing
0000437: 5796: General: JRIpcServerThreaded::Thread: Start
0000437: 5796: General: JRIpcServerThreaded::Thread: Starting server loop for: JRWeb Client {16D404AE-0136-4DB8-94BC-F9AEB5F64A03}
0000016: 6040: General: JRWebApp::InitInstance: Start
0000016: 6040: General: JRWebApp::InitInstance: Parsing command line
0000016: 6040: General: JRWebApp::InitInstance: Get parent window and process
0000016: 6040: General: JRWebApp::InitInstance: Creating callback client
0000016: 6040: General: JRWebApp::InitInstance: Loading IE engine
0000016: 6040: General: JRWebApp::InitInstance: Creating interface server
0000016: 2668: General: JRIpcServerThreaded::Thread: Start
0000016: 2668: General: JRIpcServerThreaded::Thread: Starting server loop for: JRWeb Server {16D404AE-0136-4DB8-94BC-F9AEB5F64A03}
0000016: 6040: General: JRWebApp::InitInstance: Creating window
0000031: 6040: General: JRWebApp::InitInstance: Finish (15 ms)
0000031: 6040: General: JRWebApp::Run: Start
0000031: 6040: General: JRWebApp::Run: Running message loop
0000561: 3104: General: CViewHeaderWnd::Initialize: Start
0000561: 3104: General: CViewHeaderWnd::Initialize: Finish (0 ms)
0000561: 3104: General: CMCViewContainerWnd::Create: Finish (124 ms)
0000577: 3104: General: CMainUIWnd::SetMCView: Loading view
0000577: 3104: Store: JRMediaNetSoap::JRMediaNetSoap: Start
0000577: 3104: Store: JRMediaNetSoap::JRMediaNetSoap: Finish (0 ms)
0000577: 3104: Store: JRMediaNetStore::JRMediaNetStore: Start
0000577: 3104: Store: JRMediaNetStore::JRMediaNetStore: Finish (0 ms)
0000593: 3104: General: CWebView::Refresh: Start
0000593: 3104: General: CWebView::Refresh: Finish (0 ms)
0000593: 3104: General: CMainUIWnd::SetMCView: Finishing view creation
0000608: 3104: General: CMainUIWnd::SetMCView: View creation time: 187
0000624: 3104: General: CMainUIWnd::Resize: Start
0000686: 3104: General: CMainUIWnd::Resize: Finish (62 ms)
0000764: 3104: General: CMainUIWnd::SetMCView: View show / update time: 156
0000764: 3104: General: CMainUIWnd::SetMCView: Finish (343 ms)
0000764: 3104: General: CMCPlayerApp::InitInstance: Starting loader thread
0000764: 3104: General: CLoaderThread::PerformAction: Start
0000764: 3104: General: CLoaderThread::PerformAction: Action 8 (thread id = 3104)
0000780: 3104: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0000780: 3104: General: CLoaderThread::PerformAction: Finish (16 ms)
0000780: 3104: General: CLoaderThread::PerformAction: Start
0000780: 3104: General: CLoaderThread::PerformAction: Action 14 (thread id = 3104)
0000780: 3104: SDK: CMJAutomation::CMJAutomation: Global Count: 1, Main 0, 2e26ab8
0000780: 3104: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0000780: 3104: General: CLoaderThread::PerformAction: Finish (0 ms)
0000780: 3104: General: CMCPlayerApp::InitInstance: Version: JRiver Media Center 16.0.116 (registered)
0000780: 3104: General: CMCPlayerApp::InitInstance: Finish (780 ms)
0000780: 2488: General: CLoaderThread::Thread: Start
0000811: 3104: General: CWebViewWebWnd::OnBeforeNavigate: Start
0000811: 3104: General: CWebViewWebWnd::OnBeforeNavigate: URL: C:\Program Files (x86)\J River\Media Center 16\Data\Default Webpages\English\Start\index.html
0000827: 3104: General: CWebViewWebWnd::OnBeforeNavigate: Finish (16 ms)
0000827: 3104: General: CLoaderThread::PerformAction: Start
0000827: 3104: General: CLoaderThread::PerformAction: Action 20 (thread id = 3104)
0000827: 3104: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0000827: 3104: General: CLoaderThread::PerformAction: Finish (0 ms)
0002012: 3104: General: CWebViewWebWnd::OnTitleChange: Start
0002012: 3104: General: CWebViewWebWnd::OnTitleChange: Title: index.html
0002012: 3104: General: CWebViewWebWnd::OnTitleChange: Finish (0 ms)
0002028: 3104: General: CWebViewWebWnd::OnTitleChange: Start
0002028: 3104: General: CWebViewWebWnd::OnTitleChange: Title: Start
0002028: 3104: General: CWebViewWebWnd::OnTitleChange: Finish (0 ms)
0002168: 3104: General: CMCResourceHelper::GetIsModalPopupShowing: Menu showing
0003151: 3104: General: CMCResourceHelper::GetIsModalPopupShowing: Menu showing
0003479: 3104: General: CLoaderThread::PerformAction: Start
0003479: 3104: General: CLoaderThread::PerformAction: Action 12 (thread id = 3104)
0003479: 3104: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0003479: 3104: General: CLoaderThread::PerformAction: Finish (0 ms)
0003588: 3104: General: CLoaderThread::PerformAction: Start
0003588: 3104: General: CLoaderThread::PerformAction: Action 0 (thread id = 3104)
0003588: 3104: General: CLoaderThread::PerformAction: Creating zones
0003588: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Start
0003588: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Creating
0003588: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Initializing
0003588: 3104: SDK: CMJAutomation::CMJAutomation: Global Count: 2, Main 0, 2e26de8
0003588: 3104: Playback: CDisplayPlugin::LoadPlugin: Start
0003588: 3104: Playback: CDisplayPlugin::LoadPlugin: Plugin: Cover Art
0003588: 3104: Playback: CDisplayPlugin::LoadPlugin: Finish (0 ms)
0003588: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Updating for program state
0003588: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Updating volume / mute settings
0003635: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Updating playback state, mixer state, etc.
0003635: 3104: Playback: CPlayerZone::CreatePlaybackEngine: Finish (47 ms)
0003635: 3104: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0003635: 3104: General: CLoaderThread::PerformAction: Finish (47 ms)
0004680: 2488: General: CLoaderThread::PerformAction: Start
0004680: 2488: General: CLoaderThread::PerformAction: Action 23 (thread id = 2488)
0004680: 2488: General: CLoaderThread::PerformAction: Waiting... (100 ms)
0004680: 4812: General: CSuggestHelper::Thread: Start
0004680: 4812: General: CSuggestHelper::Thread: Finish (0 ms)
0004789: 2488: General: CLoaderThread::PerformAction: Finish (109 ms)
0004789: 3104: General: CLoaderThread::PerformAction: Start
0004789: 3104: General: CLoaderThread::PerformAction: Action 1 (thread id = 3104)
0004789: 3104: General: CLoaderThread::PerformAction: Processing startup playback settings
0004789: 3104: General: CLoaderThread::PerformAction: Processing recording command line
0004789: 3104: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0004789: 3104: General: CLoaderThread::PerformAction: Finish (0 ms)
0005507: 3104: General: CMCResourceHelper::GetIsModalPopupShowing: Main window disabled
0005507: 3104: General: RunProgram: Start
0005507: 3104: General: RunProgram: Filename: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Log.txt / Parameters:
0005507: 3104: General: RunProgram: Performing ShellExecute...
0005585: 3104: General: RunProgram: Running process...
0005585: 3104: General: RunProgram: Finish (78 ms)
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #8 on: June 24, 2011, 04:36:34 pm »

The prior post is not the entire log - had to cut a bunch off to get it to fit in the forum window.  Too bad I can't just attach a text file to the forum.
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #9 on: June 24, 2011, 04:38:40 pm »

The snippet posted just shows a normal startup.

Try posting the last few hundred lines of the 'Previous Log' instead.  They will show the shutdown.
Logged
Matt Ashland, JRiver Media Center

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #10 on: June 24, 2011, 04:43:32 pm »

OK - will do - but now MC is behaving again - as soon as it slows down I'll snag the log and post it.  The last log was in fact the last few hundred lines just fyi.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: Long Time Shutdown Response
« Reply #11 on: June 24, 2011, 04:44:31 pm »

Could it be from a disk that has spun down?  In other words, does it happen when you've not accessed the disk in a while?
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #12 on: June 24, 2011, 04:45:04 pm »

OK - will do - but now MC is behaving again - as soon as it slows down I'll snag the log and post it.  The last log was in fact the last few hundred lines just fyi.

It was the current log.  The one where you started and looked at the log.

After a shutdown and restart, you'll need to look at the 'Previous Log'.
Logged
Matt Ashland, JRiver Media Center

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #13 on: June 24, 2011, 04:48:46 pm »

OK - another slow shutdown - here's the Previous Log - not much in there.


Media Center; Version: 16.0.116; Types: 16383
0000000: 772: General: Starting logging: Date: 6/24/2011 4:42 PM
0000000: 772: General: Log Reset: Logging reset
0002543: 772: General: CMCResourceHelper::GetIsModalPopupShowing: Main window disabled
0002543: 772: General: RunProgram: Start
0002543: 772: General: RunProgram: Filename: C:\Users\Dan\AppData\Roaming\J River\Media Center 16\Log.txt / Parameters:
0002543: 772: General: RunProgram: Performing ShellExecute...
0002574: 772: General: RunProgram: Running process...
0002574: 772: General: RunProgram: Finish (31 ms)
0007004: 772: General: CMCResourceHelper::GetIsModalPopupShowing: Main window disabled
0008205: 772: General: CMCResourceHelper::GetIsModalPopupShowing: Main window disabled
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #14 on: June 24, 2011, 04:53:02 pm »

Here's another stab at it: Again only the last few hundred lines.


Media Center; Version: 16.0.116; Types: 16383

0137063: 4240: General: CMCToolsCore::Destroy: Destroying CD manager
0137063: 4240: General: CMCToolsCore::Destroy: Destroying auto-play
0137063: 4240: General: CMCToolsCore::Destroy: Destroying download queue
0137063: 4240: General: CMCToolsCore::Destroy: Destroying convert helper
0137063: 4240: General: CMCToolsCore::Destroy: Destroying CD writers
0137063: 4240: General: CMCToolsCore::Destroy: Destroying interface plugins
0137063: 4240: General: CMCToolsCore::Destroy: Destroying store manager
0137063: 4240: General: CMCToolsCore::Destroy: Destroying TV guide scanner
0137063: 4240: General: CMCToolsCore::Destroy: Destroying TV control
0137063: 4240: General: CMCToolsCore::Destroy: Destroying inactivity timer
0137063: 4240: General: CMCToolsCore::Destroy: Destroying Google Account
0137063: 4240: General: CMCToolsCore::Destroy: Destroying DLNA
0137063: 4240: General: CMCToolsCore::Destroy: Destroying web links managager
0137063: 4240: General: CMCToolsCore::Destroy: Destroying Last.fm
0137063: 4240: General: CMCToolsCore::Destroy: Destroying Wikipedia manager
0137063: 4240: General: CMCToolsCore::Destroy: Destroying menu command helpers
0137063: 4240: General: CMCToolsCore::Destroy: Destroying recorder
0137063: 4240: General: CMCToolsCore::Destroy: Destroying converter
0137063: 4240: General: CMCToolsCore::Destroy: Destroying audio analyzer
0137063: 4240: General: CMCToolsCore::Destroy: Destroying skin manager
0137063: 4240: General: CMCToolsCore::Destroy: Destroying plugin manager
0137063: 4240: General: CMCToolsCore::Destroy: Destroying print wizard
0137063: 4240: General: CMCToolsCore::Destroy: Destroying image editor
0137063: 4240: General: CMCToolsCore::Destroy: Finish (0 ms)
0137063: 4240: General: CMCCore::Destroy: Deleting Player
0137063: 4240: General: CMCCore::Destroy: Deleting DB
0137063: 4240: Database: MCDB::Unload: Start
0137063: 4240: Database: MCDB::Unload: Stopping worker threads
0137063: 4240: Database: MCDB::Unload: Getting database lock
0137063: 4240: Database: MCDB::Unload: Starting unload
0137063: 4240: Database: MCDB::Unload: Updating child objects after unload
0137063: 4240: Database: MCDB::Unload: Resetting info
0137063: 4240: Database: MCDB::Unload: Finish (0 ms)
0137063: 4240: General: CMCCore::Destroy: Deleting Router
0137063: 4240: General: CMCCore::Destroy: Deleting Factory
0137063: 4240: General: CMCCore::Destroy: Deleting Flavor
0137063: 4240: General: CMCCore::Destroy: Finish (0 ms)
0137063: 4240: General: CMCShutdownHelper::Cleanup: Updating running flags
0137063: 4240: General: CMCShutdownHelper::Cleanup: Deleting frame
0137063: 4240: General: CMainFrame::OnDestroy: Start
0137063: 4240: General: CMCShutdownHelper::Cleanup: Start
0137063: 4240: General: CMCShutdownHelper::Cleanup: Source: CMainFrame - WM_DESTROY
0137063: 4240: General: CMCShutdownHelper::Cleanup: Finish (0 ms)
0137063: 4240: General: CMainFrame::OnDestroy: Finish (0 ms)
0137078: 4240: General: CMCShutdownHelper::Cleanup: Deleting global objects
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #15 on: June 24, 2011, 04:54:21 pm »

The number on the far left is the time, in milliseconds.

So that last snippet spanned 15ms (the blink of an eye).

You might read up and see where the times make a big jump.
Logged
Matt Ashland, JRiver Media Center

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #16 on: June 24, 2011, 04:58:05 pm »

Hey - I know how to tell time and when it takes 60 plus seconds for the MC process to stop - I know it!  I've replied to your email with the Previous Log - - in full.  Maybe you can have a look at that.

MC is failing somehow - it's even slower than iTunes - which is not what I bargained for.
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: Long Time Shutdown Response
« Reply #17 on: June 24, 2011, 05:47:14 pm »

coffeethecat, I think you've misunderstood Matt.  He was indicating that the most recent log snippet only shows 15ms worth of log data, so he can't glean any more information from the data.  Matt was asking for you to examine the logs, probably working backwards, to notice when there is a big time gap between commands.
Logged
The opinions I express represent my own folly.

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: Long Time Shutdown Response
« Reply #18 on: June 24, 2011, 05:52:32 pm »

Shutdown should be instant.  What you're seeing is not normal.  

But make sure you get the right log.  The previous log will be where you find the information, and it won't appear there until shutdown is complete, so wait another minute before you look.

Maybe you missed this:
Quote
Could it be from a disk that has spun down?  In other words, does it happen when you've not accessed the disk in a while?

Is there anything that isn't "stock"?  Take a minute and describe your setup.
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #19 on: June 25, 2011, 08:22:15 am »

Update:  Since this problem was not consistent, I started thinking that maybe MC was attempting to do some kind of updating, at certain times, maybe cover art or whatever - so - I just left MC running all night on my PC and this morning I've started and stopped it many many times and it seems to have stabilized.  I'll just run with it for now and report back if there's any further degradation to the response time.

Thanx for your help.

Dan
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #20 on: June 25, 2011, 08:41:48 am »

Dang!  Spoke too soon.  Thought the problem went away - but no - it's back - long time to shutdown again.  I give up!  What an annoying quirk of MC.  Do you think if I did a complete uninstall and re-install that it may help?  I'm out of ideas.  I wish I could send you the complete log file somehow.
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2556
Re: Long Time Shutdown Response
« Reply #21 on: June 25, 2011, 09:03:01 am »

You can e-mail the log to matt at jriver.

Have you built all of your thumbnails already? Are you analyzing audio? Do you have any library server clients connected?

The log should tell you what's going on. Look for huge gaps between the far left numbers.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: Long Time Shutdown Response
« Reply #22 on: June 25, 2011, 09:49:05 am »

Please read my last post and answer.

Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #23 on: June 25, 2011, 09:59:57 am »

I've emailed the log.  My install, except for the DSP add on - is vanilla.  And I only added the DSP app this morning.  My system is a W7 box with 8GB of ram.  1tb system disk and my music is on a 1.5tb external Seagate drive.  I also run iTunes - but never simultaneously.  I've noticed that when I click on the X to shutdown MC, and go to the Task Manager to watch the procless - it always reads MC Not Responding.  Not sure if this helps.  Thanx .... Dan
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #24 on: June 25, 2011, 10:08:26 am »

Thanks for the log.

It shows a shutdown that took 2 seconds.  It was slow because there was some tagging that had to finish.

But this isn't anywhere near the 30 seconds you're reporting.  So either it's getting stuck after the last line in the log (rare), or that wasn't a log of one of the slow shutdowns.

Do you have to kill the process or does it eventually go away?  What happens if you try to run Media Center again while the old one is stuck in Task Manager?
Logged
Matt Ashland, JRiver Media Center

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #25 on: June 25, 2011, 10:19:31 am »

I do not have to kill the process. It will eventually - way more than 2 second btw - go away - it's taking about 30-60secs.   If I try to launch MC again while the process is trying to stop - MC will not launch.  I'm going to send you the most recent log again. Hopefully it'll show you what I'm seeing this time.
Logged

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #26 on: June 25, 2011, 10:24:10 am »

Here's maybe a clue.  If I launch MC and do nothing else - don't play any tunes - do absolutely nothing - - and just shut it down - it goes right down.  However, if I start a tune and then try a shutdown - it does its slow shutdown thing.  Does this help?
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2556
Re: Long Time Shutdown Response
« Reply #27 on: June 25, 2011, 11:36:07 am »

Could be a soundcard issue. Have you tried updating your drivers?
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #28 on: June 25, 2011, 12:45:30 pm »

The last log shows that auto-import is being slow to shutdown.

For now, disable the 'Analyze audio' feature for auto-import.

I'll follow-up next week once I can look at the source code with more information about a fix.

Thanks.
Logged
Matt Ashland, JRiver Media Center

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #29 on: June 27, 2011, 02:35:12 pm »

What types of audio files are in your library?  WAV, AIFF, MP3, etc.?  About how many of each?

Thanks.
Logged
Matt Ashland, JRiver Media Center

coffeethecat

  • World Citizen
  • ***
  • Posts: 102
Re: Long Time Shutdown Response
« Reply #30 on: June 27, 2011, 02:45:05 pm »

About 65,000 tunes (some videos - less than 100)  - mostly .mp3 - I'd say about 80% - the rest is a mix of .wav,  .mp4, .wmv, and the like.  All my data is on an external 1.5tb drive. 

Followup:  I did a "complete uninstall" with my "Total Uninstall V5" software - which rips out all of the Registry entries for any uninstalled product.  I reinstalled MC16.  Rebuilt my Libraries - did not activate the "Analyse Audio" switch - and it's running fine now for about 48 hours.

Dan
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 41969
  • Shoes gone again!
Re: Long Time Shutdown Response
« Reply #31 on: June 27, 2011, 02:55:41 pm »

Coming in 16.0.120:
Fixed: With analyze audio enabled in Auto-Import, shutdown could take longer than expected in some cases.

The issue is that it takes a little extra time for the analyzer to figure out if it can natively decode WAV and AIFF files (requires opening the file's header).  We weren't checking cancel while doing this, so if you shutdown once it started, you wouldn't be able to shutdown until it finished.
Logged
Matt Ashland, JRiver Media Center
Pages: [1]   Go Up