INTERACT FORUM

Please login or register.

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

Author Topic: MC17 crashes after closing Theater view in fullscreen exclusive mode  (Read 1130 times)

Shogun

  • Recent member
  • *
  • Posts: 6

Crash occures with 17.0.98, but it is the same with 17.0.82.
Unticked, it works flawlessly, but without this option it's a bit laggy on my htpc.

Only solution so far is loading a video before entering theater view.

Hardware:

Intel Atom D2700
4 GB Ram

Log:

Media Center; Version: 17.0.98; Types: 1

0004197: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Menu showing
0004212: 508: General: CMCUICore::SetMode: Start
0004212: 508: General: CMCUICore::SetMode: Setting UI mode: 3
0004322: 508: General: CMCUICore::UpdateScreenResolution: Start
0004322: 508: General: CMCUICore::UpdateScreenResolution: Default fullscreen settings:
0004322: 508: General: CMCUICore::UpdateScreenResolution: Monitor changed to monitor: 0
0004322: 508: General: CMCUICore::UpdateScreenResolution: Changing settings to:
0004353: 508: General: CMCUICore::UpdateScreenResolution: Finish (31 ms)
0004353: 508: General: CMainUIWnd::Resize: Start
0004368: 508: General: CDXCore::Initialize: Start
0004368: 508: General: CDXCore::Initialize: Stopping previous instances
0004368: 508: General: CDXCore::Terminate: Start
0004368: 508: General: CDXCore::Terminate: DestroyObjects
0004368: 508: General: CDXCore::Terminate: Release Direct3D
0004368: 508: General: CDXCore::Terminate: Unload D3D.dll
0004368: 508: General: CDXCore::Terminate: Clearing variables
0004368: 508: General: CDXCore::Terminate: Finish (0 ms)
0004368: 508: General: CDXCore::Initialize: Creating Direct3D
0004400: 508: General: CDXCore::Initialize: Loading D3DX
0004400: 508: General: CDXCore::Initialize: Choosing adapter
0004400: 508: General: CDXCore::Initialize: Testing capabilities
0004400: 508: General: CDXCore::Initialize: Adapter: 0
0004400: 508: General: CDXCore::Initialize: Vendor Id: 32902
0004400: 508: General: CDXCore::Initialize: Device Id: 3042
0004400: 508: General: CDXCore::Initialize: Getting depth stencil format
0004400: 508: General: CDXCore::Initialize: Creating device
0004478: 508: General: CDXCore::Initialize: Success
0004478: 508: General: CDXCore::Initialize: Finish (110 ms)
0004478: 508: General: CMainUIWnd::Resize: Finish (125 ms)
0004493: 508: General: CMCUICore::SetMode: Finish (281 ms)
0004602: 3584: General: CLoaderThread::PerformAction: Start
0004602: 3584: General: CLoaderThread::PerformAction: Action 23 (thread id = 3584)
0004602: 3584: General: CLoaderThread::PerformAction: Waiting... (100 ms)
0004602: 2828: General: CSuggestHelper::Thread: Start
0004602: 2828: General: CSuggestHelper::Thread: Finish (0 ms)
0004805: 3584: General: CLoaderThread::PerformAction: Finish (203 ms)
0004805: 508: General: CLoaderThread::PerformAction: Start
0004805: 508: General: CLoaderThread::PerformAction: Action 1 (thread id = 508)
0004805: 508: General: CLoaderThread::PerformAction: Processing startup playback settings
0004805: 508: General: CLoaderThread::PerformAction: Processing recording command line
0004805: 508: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0004805: 508: General: CLoaderThread::PerformAction: Finish (0 ms)
0005726: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005726: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005866: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005866: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005866: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005866: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005866: 508: General: CMCResourceHelper::GetIsModalPopupShowing: Message box showing
0005882: 508: General: CLoaderThread::PerformAction: Start
0005882: 508: General: CLoaderThread::PerformAction: Action 6 (thread id = 508)
0005882: 508: General: CLoaderThread::PerformAction: Waiting... (0 ms)
0005882: 508: General: CLoaderThread::PerformAction: Finish (0 ms)
0005882: 508: General: CMCUICore::SetMode: Start
0005882: 508: General: CMCUICore::SetMode: Setting UI mode: -999
0005928: 508: General: CDXCore::Terminate: Start
0005928: 508: General: CDXCore::Terminate: DestroyObjects
0005944: 508: General: CDXCore::Terminate: Release Direct3D
0006038: 508: General: CDXCore::Terminate: Unload D3D.dll
0006100: 508: General: CDXCore::Terminate: Clearing variables
0006100: 508: General: CDXCore::Terminate: Finish (172 ms)
0006100: 508: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
0006100: 508: General: TopLevelExceptionFilter: Message: 33769, wParam: 69371568, lParam: 1, Window class: MJFrame
0006100: 508: General: TopLevelExceptionFilter: MCC: 22009, Param: -999
0007098: 3584: General: CLoaderThread::PerformAction: Start
0007098: 3584: General: CLoaderThread::PerformAction: Action 4 (thread id = 3584)
0007098: 3584: General: CLoaderThread::PerformAction: Entering DisablingConflictingSoftware
0007098: 3584: General: CLoaderThread::PerformAction: Back from DisablingConflictingSoftware
0007098: 3584: General: CLoaderThread::PerformAction: Waiting... (100 ms)
0010140: 3840: General: JRWebApp::Destroy: Start
0010140: 3840: General: JRWebApp::Destroy: Finish (0 ms)
0010140: 3840: General: JRWebApp::Run: Finish (9999 ms)
0010140: 3840: General: JRWebApp::ExitInstance: Start
0010140: 3840: General: JRWebApp::ExitInstance: Stopping web engine
0010140: 3840: General: JRWebApp::ExitInstance: Stopping callback server
0010140: 3840: General: JRWebApp::ExitInstance: Stopping interface server
0010140: 3840: General: JRIpcServerThreaded::ServerStop: Start
0010140: 3840: General: JRIpcServerThreaded::ServerStop: Cancelling thread
0010140: 3840: General: JRIpcServerThreaded::ServerStop: Cancelling pending run
0010140: 3840: General: JRIpcServerThreaded::ServerStop: Stopping thread
0010140: 964: General: JRIpcServerThreaded::Thread: Thread finishing (cancel: 1; errors: 1)
0010140: 964: General: JRIpcServerThreaded::Thread: Finish (10015 ms)
0010156: 3840: General: JRIpcServerThreaded::ServerStop: Cancelling response threads
0010156: 3840: General: JRIpcServerThreaded::ServerStop: Deleting response threads
0010156: 3840: General: JRIpcServerThreaded::ServerStop: Closing notification window
0010156: 3840: General: JRIpcServerThreaded::ServerStop: Finish (16 ms)
0010156: 3840: General: JRWebApp::ExitInstance: Finishing
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72446
  • Where did I put my teeth?
Re: MC17 crashes after closing Theater view in fullscreen exclusive mode
« Reply #1 on: March 01, 2012, 06:15:30 pm »

Welcome to the forum.  Could you update your video driver?  It looks like the crash happens when MC switches from 3D drawing.
Logged

Shogun

  • Recent member
  • *
  • Posts: 6
Re: MC17 crashes after closing Theater view in fullscreen exclusive mode
« Reply #2 on: March 01, 2012, 06:31:01 pm »

I already use the latest driver (8.14.8.1073).
Older Drivers doesn't help either.

Seems like Intel is incapable to create unproblematic VGA drivers.

But thanks for your reply. Very appreciated. :)
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72446
  • Where did I put my teeth?
Re: MC17 crashes after closing Theater view in fullscreen exclusive mode
« Reply #3 on: March 01, 2012, 07:36:56 pm »

Video cards are cheap.
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42388
  • Shoes gone again!
Re: MC17 crashes after closing Theater view in fullscreen exclusive mode
« Reply #4 on: March 01, 2012, 07:41:53 pm »

The advanced Theater View option for exclusive drawing is experimental and not recommended.  I can't reproduce a crash using it, but the option may not work with all hardware.

Most hardware should not need exclusive drawing for smooth Theater View animations. 

You could try turning down the settings in Options > General > Video Card.
Logged
Matt Ashland, JRiver Media Center

Shogun

  • Recent member
  • *
  • Posts: 6
Re: MC17 crashes after closing Theater view in fullscreen exclusive mode
« Reply #5 on: March 01, 2012, 08:06:47 pm »

@ Matt

That does the trick, but it isn't really a smooth experience without this option.

Misunderstanding...it doesn't matter which setting or resolution i set....problem remains...

Theater View is only "nice-to-have", because this system is only for music playback (low power consumption) with a Xonar Essence ST.

Anyway, thank you for taking your time. :)
Logged
Pages: [1]   Go Up