Log in

View Full Version : 2.5.8 crashes x264.exe and ffmpeg.exe, 2.5.7 doesn't.


Redsandro
2nd July 2009, 20:05
Hi,

Following this recommendation:
About this page

The best place to report Avisynth bugs is http://forum.doom9.org/forumdisplay.php?f=69
I thought I'd let you know that on my Windows 7 x64 machine, AviSynth 2.5.8 causes both x264.exe (all versions) and ffmpeg.exe (all versions) to crash.

Ofcourse I didn't check all versions but at least the latest one and some versions from the past 2 years.

I am not a programmer and haven't got a clue what the problem is. I'll just use 2.5.7 again from now on. To me AviSynth seems to be the problem because replacing it fixes it. However if not and I'm too foolish to realise, I am very sorry for this post. But for one is interested, here's the backtrace I got from x264.exe with 2.5.8 installed:

http://forum.doom9.org/showpost.php?p=1302140&postcount=10

I thought it worked fine on XP64, but honestly, with my image mess of OSses and interchanging them a lot, I am not sure anymore.

Adub
2nd July 2009, 21:05
Part of it could be due to the fact that you are running a 32 bit process on a 64 bit machine. Now, normally people have been able to complete this process just fine, but if 2.5.7 works for you, and nothing in 2.5.8 is necessary to you, then why not use 2.5.7?

Redsandro
2nd July 2009, 21:42
Yep, that works just fine. Until ofcourse I find that new feature I need.

Though I thought since 32 bit apps usually commonly work just fine on Win64 architecture, maybe a certain routine just needs to be written differently to do the same without crashing on a Win7 x64 host.

SEt
2nd July 2009, 21:57
Yes, regular user-mode programs like x264, ffmpeg and avisynth should work without problems on x64 Windows. But remember that Win7 is just a beta and not the release yet, so this can be the reason.

Redsandro
2nd July 2009, 22:01
I am running a recent post-RC build, RTM changes will be minimal if any. But I'll check again when I have RTM. Probably takes a few months before it's sold in the student store.

rkalwaitis
8th July 2009, 16:29
Are you using the mt_masktools-26.dll? If this is the new goodie you are talking about, try using mt_masktools-25.dll. The -26 would cause my .x264 to crash occassionally.

But I have a 64 bit and all seems fine.

Redsandro
8th July 2009, 16:41
I wasn't using it, but it was indeed in my plugins folder. I'm not sure if that makes it related, because it's still in my plugins folder and now that I run avs 2.5.7, nothing crashes anymore.
Note however that x264 and ffmpeg crashed all the time without exceptions, in stead of occasionally.

rkalwaitis
8th July 2009, 21:35
But if its in your plugin folder it is loaded when you use the masktools. Any easy way to check it would be to remove it from the folder and leave the mt_masktools-25.dll, tnen try eith the 2.5.8 version again and see if it works. I know that the mt_masktools-26.dll was my problem. Both should not be in your plugins folder anyways. and the -25 version seems to work okay with the 2.5.8 avisynth as well. Are you using MEGUI?

Redsandro
8th July 2009, 22:00
Yep I was using MeGUI, but during the "???" moment I used the command line to find out if a certain option was the cause.
Turned out only specifying input with -o NUL is enough to break it. Same (sort of) with ffmpeg.

At the moment I don't want to install 2.5.8 again because it (2.5.7) works fine now, I don't think the plugin is the problem (because I got it recently and the problem was there from the start (which is me getting Windows 7)) and other people suggested I wait for Win7 RTM before I check for problems again.

IanB
8th July 2009, 23:53
mt_masktools-26.dll is for use only with early interim build of 2.6.0 in all other version of avisynth it will cause a variety of problems because it will access memory outside of the defined structures, with 2.5.8 it is crashing, with 2.5.7 it will still be doing wierdness, it is just not crashing, think yourself lucky.

Redsandro
8th July 2009, 23:56
Ah ok I see. I have mutilated their extensions just in case.
(.dll.bak)