Topic: Crash on start for certain files

MPC crashes on start on certain files, tried both core and stand alone installation.
I can provide logs to help troubleshoot if necessary, but here is the MPC log dump:

kernelbase!RaiseException+0x48
msvcr90!_CxxThrowException+0x48
msvcr90!operator new+0x64

https://drdump.com/Problem.aspx?Problem … ogin=guest

Thanks

Re: Crash on start for certain files

seanami
MPC crashes on start on certain files

what kind of files?

I can provide logs

yes please

Re: Crash on start for certain files

Certain anime in MKV container, H264 8-bit:
http://imgur.com/eAkqt0N

What logs would you like me to pull other than the MPC-HC crash log I provided?

  • MAG79
  • SVP developer
  • Offline

Re: Crash on start for certain files

seanami
It is maybe lack of memory bug.
Check file last launch log in the SVP tray menu - Information - Last launch log
What is written there? Is player needed 4GB patch?

Re: Crash on start for certain files

Seems its an Avisynth crash
http://pastebin.com/95j7fhB3

Re: Crash on start for certain files

you're out of memory for 32-bit process

Intel Core i7-5960X

lower "processing threads" value to 19

Re: Crash on start for certain files

Worked, thanks
Curious if there was a change in 3.1.6 to 3.1.7 in determining auto number of threads?
Auto used to work fine in 3.1.6

  • MAG79
  • SVP developer
  • Offline

Re: Crash on start for certain files

seanami
3.1.6 and 3.1.7 uses the same threads number when select auto. No changes here.
I think it is influence of other new components: MPC-HC, LAV Filters, madVR.

9 Reply by xenonite (edited by xenonite 18-07-2015 06:28:55)

  • Thanks: 17

Re: Crash on start for certain files

seanami
Maybe you could also try setting "processing threads" to 24 or 26.

The reason I am suggesting that is because I have the exact same CPU model as you (and it seems the same monitor as well, Asus ROG Swift, no?) and 26 threads allows me to completely "max out" the normal profile settings without dropping frames, while lowering the number of threads results in reduced CPU utilization and the accompanying frame drops that go with it (if the quality settings are not lowered).
I do get the occasional script restart due to "memory leak detection" and sometimes MPC-HC crashes, but the increased interpolation accuracy is well worth it to me.

As always though, if you are happy with the current performance at 19 threads then it might not be the best idea to fix what is not broken... smile

Ps. I saw your MadVR settings screenshot and have you ever tried increasing your "render queue" so that it is more than your "present queue"? It might also help with stability and smoothness.