This doesn't look good.
Thead 4288 is the main thread:
0000000: 4288: General: Starting logging: Date: 5/1/2014 7:39 pm
So, it goes along for a little bit and loads the default library here:
0003635: 4288: Database: MCDB::Load: Loading from path: C:\Users\myrna\AppData\Roaming\J River\Media Center 19\Library\
Then it handles some resizing stuff for the main UI window, and starts loading the Startup View:
0003885: 4288: General: CMainUIWnd::Resize: Finish (94 ms)
0003885: 4288: General: CMCUICore::SetMode: Finish (109 ms)
0003885: 4288: General: CMCPlayerApp::InitInstance: Showing startup view
0003901: 4288: General: CMainUIWnd::SetMCView: Start
0003901: 4288: General: CMainUIWnd::SetMCView: View info name: Start
0003901: 4288: General: CMainUIWnd::SetMCView: Hiding old view
0003901: 4288: General: CMainUIWnd::SetMCView: Creating new view
Then it initializes some extra threads. Stuff starts going badly pretty quickly.
It loads the View Container Window:
0003901: 4288: General: CMCViewContainerWnd::Create: Start
0003901: 4288: General: CMCViewContainerWnd::Create: Creating window
0003901: 4288: General: CMCViewContainerWnd::Create: Initializing
0003901: 4856: General: JRIpcServerThreaded::Thread: Start
0003901: 4856: General: JRIpcServerThreaded::Thread: Starting server loop for: JRWeb Client {8B75DE64-4910-4052-AEF0-106CC05205B5}
Notice, we're at 3901ms after loading on the main thread. Here's the equivalent section from my Previous Log, by the way:
0001187: 3432: General: CMCViewContainerWnd::Create: Start
0001187: 3432: General: CMCViewContainerWnd::Create: Creating window
0001187: 3432: General: CMCViewContainerWnd::Create: Initializing
0001219: 8352: General: JRIpcServerThreaded::Thread: Start
0001219: 8352: General: JRIpcServerThreaded::Thread: Starting server loop for: JRWeb Client {CDD1C204-6C06-4214-A871-2E21381B513B}
I'm only at 1100ms at this point, but that can be explained by the "improper shutdown" popup dialog you got, which appears at the very head of your log and seemed to take three seconds to load:
0000032: 4288: General: CMCPlayerApp::InitInstance: Loading skin
0000156: 4288: General: CMCUICore::SystemPowerManager_UpdateActions: Start
0000156: 4288: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -2000; Playing: 0
0000156: 4288: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
0001857: 4288: General: CMCUICore::GetPopupShowing: popup showing=true, window class name=JRiver Popup Class
0003542: 4288: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
I have no similar delay in mine, but I also didn't show the popup in my log. It might have just been waiting for you to respond to the dialog for much of that time. So, I'd say we pretty much match at this point.
Then, it spawns a background reader thread, and goes away from the log for a bit, and you get one of these:
0003916: 1184: Reader: CWinINetReader::DownloadFromHTTPURL: Start
0004213: 1184: Reader: CWinINetReader::DownloadFromHTTPURL: Retry needed, trying again...
0004213: 1184: Reader: CWinINetReader::Connect: Start
0004213: 1184: Reader: CWinINetReader::Connect: Finish (0 ms)
0004696: 1184: Reader: CWinINetReader::DownloadFromHTTPURL: Success
0004696: 1184: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (780 ms)
0004696: 1184: Reader: CWinINetReader::Thread: Finish (780 ms)
0004696: 4288: Reader: CWinINetReader::Open: Finish (780 ms)
My log is riddled with that pattern, though not till a bit further down. I use the IE engine instead of Chromium though, and it looks like with Chromium it asks the JRiver servers for any updates to the engine when it loads the first time (and the initial failure is probably a redirect). So, that (in itself) doesn't look that unusual, and it returns back quickly enough.
So, it finished opening whatever from JRiver it wanted to get and the main thread comes back at 4600ms. But it still hasn't finished CMCViewContainerWnd::Create, making the view container window.
The very next lines are still the main thread:
0574802: 4288: Reader: CWinINetReader::Close: Start
0574802: 4288: Reader: CWinINetReader::Close: Finish (0 ms)
Woah, that was a jump. Then it goes away again and JRWebApp and Chromium start doing their thing in background threads. Then, finally CMCViewContainerWnd::Create comes back...
0582149: 4288: General: CViewHeaderWnd::Initialize: Start
0582149: 4288: General: CViewHeaderWnd::Initialize: Finish (0 ms)
0582149: 4288: General: CMCViewContainerWnd::Create: Finish (578248 ms)
0582149: 4288: General: CMainUIWnd::SetMCView: Loading view
578248 ms is 9 and a half minutes. That's right at the head of your log. It is not failing to do it, but is having an incredibly hard time creating the initial view container.
My Previous Log follows the same basic pattern (with differences because of IE vs Chromium but nothing too weird) but, here's mine:
0001500: 3432: General: CViewHeaderWnd::Initialize: Start
0001516: 3432: General: CViewHeaderWnd::Initialize: Finish (16 ms)
0001531: 3432: General: CMCViewContainerWnd::Create: Finish (344 ms)
0001531: 3432: General: CMainUIWnd::SetMCView: Loading view
So, that's what the problem is. It is getting stuck when trying to create the initial view window itself. The Library has long since been loaded (that happens pretty quickly and appears normal in your log).
From there on, it looks like it is doing a lot of looping and waiting for stuff to return. But it doesn't much matter, as you're 9.5 minutes in at that point.