View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000698 | madVR | bug | public | 2023-02-03 09:24 | 2023-02-08 22:20 |
| Reporter | huhn | Assigned To | madshi | ||
| Priority | normal | Severity | crash | Reproducibility | sometimes |
| Status | assigned | Resolution | open | ||
| Summary | 0000698: the media player crashes when switching to a different file or after about 10 sec | ||||
| Description | the beta version 165 is affect the release version seems totally fine. on doctor dumb the issue is usually: https://drdump.com/UploadedReport.aspx?DumpID=103685850 818228 and sometimes: https://drdump.com/UploadedReport.aspx?DumpID=103666285 713084 this issue was gone for some time but come back in the last couple of days so i had an idea why because i changed how the dac of my sound card works and was thinking that was related and saw it is madVR crashing not mpc-hc there is no madVR crash log. if clsid dumb doesn't tell you anything then there is nothing todo here i guess. as you can see i'm not alone on doctor dumb. | ||||
| Tags | No tags attached. | ||||
| madVR Version | 165 | ||||
| Media Player (with version info) | mpc-hc 2.0 | ||||
| Splitter (with version info) | lav 0.77 | ||||
| Decoder (with version info) | lav 0.77 | ||||
| Decoding | Software | ||||
| Deinterlacing | none (progressive) | ||||
| DXVA2 Scaling Active | no | ||||
| Aero / Desktop Composition | On | ||||
| Problem occurs with mode | windowed mode | ||||
| GPU Manufacturer | NVidia | ||||
| GPU Model | 1060 | ||||
| GPU Driver Version | 512.95 | ||||
|
|
It is that madVR really wants you to update to new version :) I've seen it over a year ago and debugged it back then. And by your description it is exactly the same issue. 1. madVR creates a thread with timer to display "please update your madVR build" OSD message 2. thread is detached, but it has a pointer to renderer instance 3. if you close, reload playback, meaning the old renderer is destroyed and new one is created the pointer in the detached thread becomes invalid 4. ...and after this timeout ends it tries to use it and well crashes by doing so |
|
|
ohh that's why it is back. yes that happens before and there was another madVR version which could not be updated to the newest. never excepted an overlay message could be the issue wow. |
|
|
Is there hack/trick/workaround for this? Maybe madVR can be blocked from getting the date, so the crash feature wouldn't activate? |
|
|
not again :-) that's why "some user" are not shy about it. not sure what to do now. |
|
|
Sorry about that. I'm not 100% sure why the crash happens, it only seems to happen for some people. I'll change the way the "please update your madVR version" information is shown in the next build, to avoid this crash in the future. Also, I'll probably release a new build tomorrow or the day after. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-02-03 09:24 | huhn | New Issue | |
| 2023-02-03 13:35 | kasper93 | Note Added: 0002989 | |
| 2023-02-03 16:51 | huhn | Note Added: 0002990 | |
| 2023-02-06 19:19 | mzso | Note Added: 0002991 | |
| 2023-02-07 09:01 | huhn | Note Added: 0002992 | |
| 2023-02-08 22:20 | madshi | Note Added: 0002993 | |
| 2023-02-08 22:20 | madshi | Assigned To | => madshi |
| 2023-02-08 22:20 | madshi | Status | new => assigned |
