View Issue Details

IDProjectCategoryView StatusLast Update
0000563madVRbugpublic2018-09-17 23:25
Reportercnrat Assigned Tomadshi  
PriorityhighSeveritycrashReproducibilityalways
Status closedResolutionunable to reproduce 
PlatformIntel i7 3770OSWindows 7 UltimateOS Version6.1.7601
Summary0000563: Potplayer not responding when closing after open large video
DescriptionPotplayer 1.7.12248 x64
madVR v0.92.14

Potplayer not responding when closing after open large video.

Video:
Size 8.43GB
Input AVC1 1920x1036
Output NV12 2048x1036

  (1) Built-in MKV Source
  (2) LAV Video Decoder
  (3) madVR
  (4) Built-in Audio Codec/Transform
  (5) DirectSound Audio Renderer

IMPORTANT:
The crash can not be reproduced after switching to debug mode.
Run activate debug mode.bat
Steps To ReproducePlay the video then close potplayer when playing.
Additional InformationN/A
TagsNo tags attached.
madVR Version0.92.14
Media Player (with version info)PotPlayer 1.7.12248 x64
Splitter (with version info)Unknown
Decoder (with version info)LAV Video Decoder 0.71.0
DecodingCUDA
Deinterlacingnone (progressive)
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modewindowed mode
GPU ManufacturerNVidia
GPU ModelGTX 970
GPU Driver Version398.11

Activities

madshi

2018-06-22 09:48

administrator   ~0002298

Does this problem only occur when using madVR? It does not occur when using another video renderer?

Please press Ctrl+Alt+Shift+Pause/Break to create a freeze report on your desktop, then attach the zipped txt file here.

cnrat

2018-06-22 09:54

reporter  

cnrat

2018-06-22 09:55

reporter   ~0002299

Yes. Only occur when using madVR.
Freeze report uploaded as requested.

madshi

2018-06-22 10:01

administrator   ~0002300

You created the freeze report in the situation where PotPlayer was not responding, correct?

The freeze report suggests that the main thread (which is responsible for drawing the PotPlayer GUI) does not seem to be stuck in madVR. So from looking at the freeze report, I can't see any indication that madVR would be at fault.

So what can we do now? I see 2 options:

1) Either you could ask other PotPlayer users if they can reproduce the same problem. If they can, you could report it to the PotPlayer developer and get him to fix it.

2) Or you could try to get debug information (*.pdb files or *.map files) for PotPlayer. If you have those debug files, you could then create another freeze report will should then contain more information. It's crucial that the debug information must match *exactly* the PotPlayer version you're using, otherwise it will do more harm than good.

cnrat

2018-06-22 10:03

reporter  

cnrat

2018-06-22 10:09

reporter   ~0002301

Sorry man. It is my oversight, the latest zip file is dumped when no responding.

madshi

2018-06-22 10:25

administrator   ~0002302

Ah, that freeze report makes more sense. It does show that madVR is at least involved somehow, but since madVR didn't find any debug information for PotPlayer, the freeze report is somewhat incomplete, so I can't fully see what happened. Could you try get matching debug information for PotPlayer? Not sure where you could get that from, though.

madshi

2018-09-17 23:25

administrator   ~0002376

Can't reproduce it, and no further replies, so I'm closing this for now. Feel free to reopen if you can provide more information.

Issue History

Date Modified Username Field Change
2018-06-22 02:54 cnrat New Issue
2018-06-22 09:48 madshi Note Added: 0002298
2018-06-22 09:54 cnrat File Added: madVR - freeze report.zip
2018-06-22 09:55 cnrat Note Added: 0002299
2018-06-22 10:01 madshi Note Added: 0002300
2018-06-22 10:03 cnrat File Added: madVR - freeze report_stuck.zip
2018-06-22 10:09 cnrat Note Added: 0002301
2018-06-22 10:25 madshi Note Added: 0002302
2018-09-17 23:25 madshi Note Added: 0002376
2018-09-17 23:25 madshi Status new => closed
2018-09-17 23:25 madshi Assigned To => madshi
2018-09-17 23:25 madshi Resolution open => unable to reproduce