Topic: Pressing Stop when watching Movie returns to backdrop screen but MC is frozen (Read 6133 times)

CountryBumkin · « **on:** July 07, 2013, 03:34:13 pm »

I have seen this on both computers now. When I stop a movie (with remote or using mouse on the play-bar) the movie stops and returns to the movie backdrop (DVD cover shot) but I can't get MC to do anything else. I can move the mouse pointer around but can't return to menu or restart movie.
I have to cntrl+alt+del and kill MC with the Task Manager. I am on version .206.

Could this be same problem reported here http://yabb.jriver.com/interact/index.php?topic=81789.0

CountryBumkin · « **Reply #1 on:** July 08, 2013, 04:36:03 am »

to update - I find this problem also occurs after watching/stopping recorded TV Shows.
I did more testing and the problem does not occur every time. I was able to stop some movies and MC returned to the menu as it should. Its seems like the freeze occurs if I stop quickly/soon after starting to play. When I played 5 minutes or more into the show/movie then stopped, MC worked properly. I was only able to test with about 8 movies (on two different client machines) 6 froze, 2 worked properly. Also Netflix worked properly.
I created several logs, but I don't think I'm catching anything after the freeze.

CountryBumkin · « **Reply #2 on:** July 09, 2013, 04:50:41 am »

I guess I'm the only one seeing this. Someone please test this for me. Start a movie (I'm using ifo (vob) movie) play it for about 1 minute (or less) then hit the stop button on your remote. Does your screen freeze? I can reproduce this problem on two different sets (both clients). Is it just my setup?
Once MC freezes on the cover art, I have to kill the program and restart.

6233638 · « **Reply #3 on:** July 09, 2013, 05:06:17 am »

It's working fine here, using a DVD disc.

JimH · « **Reply #4 on:** July 09, 2013, 07:02:18 am »

Stop or Pause?

CountryBumkin · « **Reply #5 on:** July 09, 2013, 08:37:45 am »

Stop.

I seems that if I let the movie play for a while (usually I play to end) and then Stop it, everything works fine. But if I start the movie then Stop it within a minute of two (like I selcted the wrong movie) it freezes MC.
Thanks for checking. If no one else is seeing this, it must be an issue with my setup.

Matt · « **Reply #6 on:** July 09, 2013, 10:09:52 am »

The logs don't clearly show a stop / switch UI mode / hang flow. So I'm not sure what's happening.

However, please see if Red October Standard vs HQ makes a difference.

Let us know what you find.

CountryBumkin · « **Reply #7 on:** July 09, 2013, 10:41:45 am »

I tried both RO std and HQ, same issue. You mentioned in another post (Crash on Stop) that an audio setting might cause a problem on stopping playback, so I check this out next.

It does seem that the problem occurs when the movie is started and stopped within a minute of so, but I did not see this issue when playing the movie to the end (not sure if this is true all the time, but it does mean it takes a lot longer to test the various scenarios).

I can reproduce this problem - but I haven't tested all the setup/configuration possibilities yet. Too bad the log doesn't show anything.

CountryBumkin · « **Reply #8 on:** July 10, 2013, 08:02:17 am »

New info -
I am still having this problem, and it does seem that if the movie/show is stopped within a minute, or so, of starting playback it will freeze MC. But if I let the movie/show play for 10+ minutes, it will not freeze MC. Could there be some communication between clients and server that takes some time to occur?

Also, maybe related, I see that the queues in madVR are running very low or empty on a couple of them. For example on the Server the queue will be like 16-26/32 but on my client (same movie) the queue is like 0-1/16. Sorry I should have brought my notes on this to work. But the general idea is that I'm seeing low queuing ("0-1") on my Client machines (both). I'll post back the exact queue names and vaules - if someone thinks it is relevant.

And the Server doesn't freeze MC when I hit the Stop button after a couple of seconds of play.

So maybe the issue is with the network.

JimH · « **Reply #9 on:** July 10, 2013, 08:39:34 am »

What happens if you use RO Std?

CountryBumkin · « **Reply #10 on:** July 11, 2013, 07:11:25 am »

I still have not figured out what is causing this problem - maybe the installation of the next MC update will take care of issue. Maybe something didn't install right.

Jim,
the problem is same whether or not I'm in RO-STD or RO-HQ. I tried different Audio setup too.
Testing with the same movie - stopping after a few minutes locks up MC, playing for 30 minutes then stopping, MC returns to menu.
This happens on all three client machines but does not happen if I play movie from Server computer. So it seems like it is a network related issue or a Client setup issue.
______________________________________________________________ ?
On the subject of MadVR queues (maybe a clue).
When I play a m2ts (VC-1) 1080x1920, 23.976fps movie using RO+HQ (on Client machine) the queues are full and stay full (decoder 31-32/32, renderer 23-24/24, present 15-16/16, etc.),

but when I play a DVD rip (ifo-vob) which is 29.9fps 720x480 resolution, the MadVR queues are "split queue 1-6/24, render queue 1-3/24, present queue 0-3/16, and frames dropped: over 1000 and climbing).

Since the queues on the m2ts rip (Blu-ray) stay full and no frames are dropped it does not appear to be a network/streaming issue. I think is something in the MadVR (or MC) settings that is wrong for playback of DVD material. Any ideas what I should look for?

nachoville · « **Reply #11 on:** July 20, 2013, 08:14:34 pm »

I'm experiencing this exact same behavior on .206 as well. Pressing Stop after some videos causes the application to freeze, sometimes displaying the backdrop and at other times just a black screen. The application doesn't crash, Task Manager lists it as "Not Responding" and it must be manually restarted.

Client / Server configuration
RO+HQ (haven't tried standard yet)

I tried reinstalling MC, but it unfortunately didn't have any effect. Log files are attached.

CountryBumkin · « **Reply #12 on:** July 21, 2013, 06:33:57 am »

I have not solved the problem either. I thought installing the latest MadVR and/or LAV versions would fix things, but it has not. I don't think this is an MC issue (or many others would have reported it by now). But hopefully the experts at JRiver and on this Forum can help figure this out.

It seems that if I watch a movie for at least 5-10 minutes then STOP it, no problem, MC goes back to the menu. But if I start a movie and then STOP it within a few minutes it freezes MC (same as your description) and I have to Cntrl+Alt+Del to "end" MC. If I hit the "Windows Key" I can open other applications (meaning computer is not frozen - just MC stops responding). The Log doesn't seem to capture anything.

I'm still trying to find the exact conditions/time that things fail. Yesterday I tried watching a Blu-ray rip and I got about half way through it when MC just stopped (is this a new problem or the same issue?). MC displayed the Cover Art screen and became unresponsive. I'm playing the same movie again on a different computer right now to see if it is computer- movie- or maybe a networking issue. Since this problem is easy to repeat I should be able to log the exact conditions when it happens.

cncb · « **Reply #13 on:** July 21, 2013, 06:58:31 am »

I reported what sounds like the same problem on the beta board. For me, it only seems to happen when I am streaming a local file on the server. That is, if I change the path of the file in MC (on the server) to a network location that can be resolved on the client so it can play it directly, it stops fine and there are no lockups.

CountryBumkin · « **Reply #14 on:** July 21, 2013, 01:43:55 pm »

What do you mean by "changing the path of the file to a network location that can be resolved"? Are you just saying it works on the Server?

I know I can play a movie from the Server without issue. The problem is happening when I play from the Client (stream to client). To me, this says there is a problem with my network. I have not changed anything regarding my network settings - but that doesn't mean something didn't change/break on its own.

cncb · « **Reply #15 on:** July 21, 2013, 02:19:38 pm »

Quote from: CountryBumkin on July 21, 2013, 01:43:55 pm

What do you mean by "changing the path of the file to a network location that can be resolved"? Are you just saying it works on the Server?

I mean change the path in the MC library to a network location instead of local (e.g "\\SERVER\Videos\Video.mkv" instead of "C:\Videos\Video.mkv"). So, when you have "Play local file if one that matches library server is found" enabled on the client it will play the file directly instead of streaming it. I have the lockups on the client when it is a local path but not when it is a network path being played directly.

nachoville · « **Reply #16 on:** July 21, 2013, 02:59:43 pm »

Under Playing From, my client shows as connected to a "library server" instead of a "local library". I'm unsure how you could modify the path to the files from local (C:\path\file) to a network/UNC path (\\server\path\file) when connected this way.

The part about "starting and stopping within a few minutes" rings very true for me as well and it may be the key to reproducing the problem. It seems to work flawlessly under normal circumstances, but as soon as you stop a video shortly after it has started it will sporadically lock up.

I don't believe it to be network related as I'm hard-wired and don't need to reboot or intervene with my router/switch to resolve the problem. My library server is dual-homed so I may connect it directly to the client in order to eliminate the router and switch from the equation. Granted even this won't resolve some oddball issues between network cards.

I'd really love to figure out what's going on here. I've sorted out 99% of the other issues I've had, but can't keep my client from locking up on occasion.

CountryBumkin · « **Reply #17 on:** July 21, 2013, 03:28:08 pm »

Quote from: nachoville on July 21, 2013, 02:59:43 pm

I don't believe it to be network related as I'm hard-wired and don't need to reboot or intervene with my router/switch to resolve the problem.

Same here. I don't reboot or reset anything - just close the non-responsive MC program and restart it. Since it only seems to a problem on the client - it seems logical that it is somehow related to streaming/networking.

cncb · « **Reply #18 on:** July 21, 2013, 04:12:19 pm »

Quote from: nachoville on July 21, 2013, 02:59:43 pm

Under Playing From, my client shows as connected to a "library server" instead of a "local library". I'm unsure how you could modify the path to the files from local (C:\path\file) to a network/UNC path (\\server\path\file) when connected this way.

You open MC on the server and change the path there.

nachoville · « **Reply #19 on:** July 22, 2013, 01:29:29 pm »

I captured a mini-dump from the most recent application hang.
The WinDbg analysis of the crash is listed below. Hopefully it will shed some light on what's happening...

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\Documents\Logs\Media Center 18\Media Center 18.DMP]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: SRV*E:\Debug-Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Mon Jul 22 10:36:15.000 2013 (UTC - 7:00)
System Uptime: 0 days 0:24:09.766
Process Uptime: 0 days 0:06:25.000
.........
wow64cpu!CpupSyscallStub+0x9:
00000000`74932e09 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify checksum for Media Center 18.exe
*** ERROR: Module load completed but symbols could not be loaded for Media Center 18.exe
*** WARNING: symbols timestamp is wrong 0x4ce7c97e 0x4a5bdadf for rasman.dll
*** WARNING: symbols timestamp is wrong 0x4ce7c83d 0x4ce7b8e8 for mswsock.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for madHcNet.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for MVRSETTINGS.DLL -
*** WARNING: Unable to verify checksum for JRTools.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for JRTools.dll -
*** WARNING: Unable to verify checksum for JRReader.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for JRReader.dll -

FAULTING_IP:
+77ad440
00000000`00000000 ?? ?

EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD: 0000000000000938

DEFAULT_BUCKET_ID: STATUS_BREAKPOINT

PROCESS_NAME: Media Center 18.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0fd

PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT

BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER: from 0000000074932cb4 to 0000000074932e09

STACK_TEXT:
00000000`0008d338 00000000`74932cb4 : 00000000`74a2452f 00000000`fff70023 00000000`00000246 00000000`0018d348 : wow64cpu!CpupSyscallStub+0x9
00000000`0008d340 00000000`7358d07e : 00000000`00000000 00000000`74931904 00000000`74a172b9 00000000`7493198b : wow64cpu!Thunk2ArgNSpNSpReloadState+0x2a
00000000`0008d400 00000000`73588a40 : 00000000`00000000 00000000`0008e130 00000000`00200246 00000000`00000000 : wow64!RunCpuSimulation+0xa
00000000`0008d450 00000000`73552c4e : 00000000`0008d7d0 00000000`00000002 00000000`0008e130 00000000`00000020 : wow64!Wow64KiUserCallbackDispatcher+0x204
00000000`0008d7a0 00000000`77101225 : 00000000`0008ebd8 00000000`00000000 00000000`00000000 00000000`fffdb000 : wow64win!whcbfnDWORD+0xe2
00000000`0008e190 00000000`7355fe4a : 00000000`7353aefe 00000000`735888d2 00000000`00001fb0 3ff00000`00000000 : ntdll!KiUserCallbackDispatcherContinue
00000000`0008e218 00000000`7353aefe : 00000000`735888d2 00000000`00001fb0 3ff00000`00000000 00000000`00000000 : wow64win!NtUserMessageCall+0xa
00000000`0008e220 00000000`735527db : 00000000`734e01de 00000000`73535460 00000000`000083e9 00000000`00000000 : wow64win!whNT32NtUserMessageCallCB+0x32
00000000`0008e270 00000000`7353b03a : 00000000`000002b1 00000000`0018fbd4 00000000`000083e9 00000000`00000000 : wow64win!Wow64DoMessageThunk+0x4b
00000000`0008e2b0 00000000`7358cf87 : 00000000`0018fb9c 00000000`fffdb000 00000000`fffdd000 00000000`7353af0c : wow64win!whNtUserMessageCall+0x12e
00000000`0008e350 00000000`74932776 : 00000000`74a2452f 00000000`73580023 00000000`00200246 00000000`0018fa84 : wow64!Wow64SystemServiceEx+0xd7
00000000`0008ec10 00000000`7358d07e : 00000000`00000000 00000000`74931920 00000000`771c5410 00000000`770decd1 : wow64cpu!TurboDispatchJumpAddressEnd+0x2d
00000000`0008ecd0 00000000`7358c549 : 00000000`00000000 00000000`00000000 00000000`73584ac8 00000000`7ffe0030 : wow64!RunCpuSimulation+0xa
00000000`0008ed20 00000000`770f4956 : 00000000`00322f80 00000000`00000000 00000000`771e2670 00000000`771b5978 : wow64!Wow64LdrpInitialize+0x429
00000000`0008f270 00000000`770f1a17 : 00000000`00000000 00000000`770f4061 00000000`0008f820 00000000`00000000 : ntdll!LdrpInitializeProcess+0x17e4
00000000`0008f760 00000000`770dc32e : 00000000`0008f820 00000000`00000000 00000000`fffdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x29220
00000000`0008f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

STACK_COMMAND: ~0s; .ecxr ; kb

FOLLOWUP_IP:
wow64cpu!CpupSyscallStub+9
00000000`74932e09 c3 ret

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: wow64cpu!CpupSyscallStub+9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wow64cpu

IMAGE_NAME: wow64cpu.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 50b8488e

FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub

BUCKET_ID: X64_APPLICATION_FAULT_STATUS_BREAKPOINT_wow64cpu!CpupSyscallStub+9

Followup: MachineOwner
---------

nachoville · « **Reply #20 on:** July 22, 2013, 04:46:24 pm »

Thanks cnbc for the suggestion. I took a slightly different approach; mapping drives from the client instead of switching to UNC paths on the library server.
As an added bonus the Theater View UI is much snappier and more responsive now. Most noticeably when navigating folders and skipping through a video (progress bar is fluid instead of moving in large chunks).

Here's the workaround in some more detail...

On the client PC, map a drive (right-click on My Computer > Map Network Drive) to the media server so the folder structure used by the server library matches the client. --> \\server\e mapped to E: on the client. Now E:\folder\filename.avi is a valid path on both the server and client.
MC > Options > Media Network > Client Options. --> Ensure "Play local file if..." option is checked.

I also left the "Auto Sync with server" option checked and was able to save a new playlist to the server so at least some client/server operations are working fine. Looks like this (apparently rare) issue is specific to rapid file playback changes via the Library Server.

Hope this helps. Cheers!

INTERACT FORUM

Author Topic: Pressing Stop when watching Movie returns to backdrop screen but MC is frozen (Read 6133 times)