View Issue Details

IDProjectCategoryView StatusLast Update
0000285madVRbugpublic2018-01-21 21:17
ReporterGCRaistlin Assigned Tomadshi  
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionunable to reproduce 
PlatformC2D E6420OSWinXPOS VersionSP3
Summary0000285: Changing refresh rate causes 100% CPU usage
DescriptionSee below.
Steps To Reproduce1. Download and open the test DVD from http://bugs.madshi.net/view.php?id=284
2. Press Pause.
3. Change the refresh rate (from 50 Hz to 60 Hz).
MPC-HC starts to eat all CPU resources. In fact, you'll hardly be able to close MPC-HC not through the console (I used Far for this).
TagsNo tags attached.
madVR Version0.87.17 and later
Media Player (with version info)MPC-HC 1.7.8.162
Splitter (with version info)LAV (internal)
Decoder (with version info)LAV (internal)
DecodingCUDA
Deinterlacingauto mode
DXVA2 Scaling Activeno
Aero / Desktop CompositionOff
Problem occurs with modewindowed mode
GPU ManufacturerNVidia
GPU ModelGF 8800 GTX
GPU Driver Version340.52

Relationships

related to 0000284 closedmadshi Going full screen and then back on the 2nd monitor causes 100% CPU usage 

Activities

madshi

2015-05-02 11:42

administrator   ~0000980

I suppose this is probably the same issue as 284. I can't reproduce this problem, either, with v0.87.21, using madVR default settings.

GCRaistlin

2015-05-02 15:53

reporter   ~0000982

Maybe, but note this issue is reproducible on the 1st monitor, too. Unfortunately I wasn't able to get a freeze report - I just couldn't wait till MPC-HC window becomes active again. If monitor refresh rate is changed by madVR the freeze doesn't occur.

madshi

2015-05-02 15:57

administrator   ~0000984

You can uncheck the option "use only if media player has keyboard focus" in the madVR "keyboard shotcuts" settings. That way the Ctrl+Alt+Shift+Break/Pause should also work if the MPC-HC window is not active.

GCRaistlin

2015-05-02 16:17

reporter  

GCRaistlin

2015-05-02 16:18

reporter   ~0000985

Done

madshi

2018-01-14 19:56

administrator   ~0002095

2.5 years later. Do you still have this issue? I was never able to reproduce it, so I wonder... FWIW, the freeze report seems to suggest that DXVA itself gets stuck for some reason, but it's not clear to me what this has to do with the refresh rate change. Also, there have been so many changes in all the software, and the driver and OS, so it might be worth to double check if the problem even still exists, anymore?

madshi

2018-01-21 21:17

administrator   ~0002166

Closing this due to lack of feedback/reply. Please feel free to reopen at any time.

Issue History

Date Modified Username Field Change
2015-04-26 01:31 GCRaistlin New Issue
2015-05-02 11:42 madshi Note Added: 0000980
2015-05-02 11:42 madshi Assigned To => madshi
2015-05-02 11:42 madshi Status new => feedback
2015-05-02 15:53 GCRaistlin Note Added: 0000982
2015-05-02 15:53 GCRaistlin Status feedback => assigned
2015-05-02 15:57 madshi Note Added: 0000984
2015-05-02 15:57 madshi Status assigned => feedback
2015-05-02 16:17 GCRaistlin File Added: madVR - freeze report (1).txt.zip
2015-05-02 16:18 GCRaistlin Note Added: 0000985
2015-05-02 16:18 GCRaistlin Status feedback => assigned
2018-01-14 19:56 madshi Note Added: 0002095
2018-01-14 19:57 madshi Status assigned => feedback
2018-01-14 19:58 madshi Relationship added related to 0000284
2018-01-21 21:17 madshi Note Added: 0002166
2018-01-21 21:17 madshi Status feedback => closed
2018-01-21 21:17 madshi Resolution open => unable to reproduce