View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000285 | madVR | bug | public | 2015-04-26 01:31 | 2018-01-21 21:17 |
Reporter | GCRaistlin | Assigned To | madshi | ||
Priority | normal | Severity | block | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Platform | C2D E6420 | OS | WinXP | OS Version | SP3 |
Summary | 0000285: Changing refresh rate causes 100% CPU usage | ||||
Description | See below. | ||||
Steps To Reproduce | 1. 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). | ||||
Tags | No tags attached. | ||||
madVR Version | 0.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) | ||||
Decoding | CUDA | ||||
Deinterlacing | auto mode | ||||
DXVA2 Scaling Active | no | ||||
Aero / Desktop Composition | Off | ||||
Problem occurs with mode | windowed mode | ||||
GPU Manufacturer | NVidia | ||||
GPU Model | GF 8800 GTX | ||||
GPU Driver Version | 340.52 | ||||
|
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. |
|
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. |
|
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. |
|
|
|
Done |
|
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? |
|
Closing this due to lack of feedback/reply. Please feel free to reopen at any time. |
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 |