[BUG] Various bugs with latest dev build (2020.09.25-21270)

[The_Tinkerer]

I tried a bunch of different ffms2 versions, including the 2016 one. No effect.

Only AviSynth on my system is in the Hybrid folder.


This may or may not be the problem:

Here's Dependency Walker for 32 bit avsviewer.exe, which works for me:




Here it is for 64 bit avsviewer64.exe, which crashes:




These 5 Microsoft dll's are in the Hybrid directory for 32 bit:

api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll

They are dated 07/16/2015, and are version 10.0.9924.0, except for locale, which is 07/16/2015 and version 10.0.10240.16384


They are NOT in the directory for AviSynth 64 bit. On my system, Dependency Walker shows that they are being linked from the Windows\System32 directory.

The 5 files I have in that directory are dated 04/12/2019, and are all version 10.0.14393.2990.

I tried some different versions of these files (putting them in the Hybrid\64bit\Avisynth folder and making sure Dependency Walker shows that they are being linked to avsviewer64.exe) and it still crashes.

To be sure, can you maybe just send me or post to google drive the 5 files that you have on your system so I can see if that's the issue? You can use Dependency Walker to verify which files avsviewer64 is actually linking and using.

---

Actually, I'm not sure if that will really have any effect. I suspect you might have some Windows 10 only API calls in avsviewer64.exe. Not sure if there is a way you can check this?

I found this, which may be or may not be relevant:

https://stackoverflow.com/questions/3847...r-computer

I know Dependency Walker results can often be misleading, which I suspect is probably the case here.