-
Notifications
You must be signed in to change notification settings - Fork 0
AVSTP rarely hangs #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I narrowed the issue down to AVSTP which is used by mvtools2: when avstp.dll is found among the autoloaded libraries, then mvtools2 is using it for its internal in-frame multithreading support. Since mvtools2 filters (MSuper, MAnalyze, MCompensate, ...) are automatically using the internally multithreaded option (mt=true default parameter), users report random crash or freeze when using scripts containing mvtools2 (e.g. QTGMC). The reproduction is so difficult that I had to either Components (64 bit versions tried)
Avisynth script (avs2.avs):
Batch file:
|
Note that I was unable to make the 1.04 release version hang on a Intel i7-11700. But on an i7-7700 processor the freeze is somewhat more reproducible. Previous night the script was running (with the original avstp release version 1.04) w/o issues for at least sixteen hours. But today the script hung "sooner" (the freeze is seen as ffmpeg output refresh is stopped): in the 12th loop at frame 40740, after 11 successful rounds - each 92466 frames.
Using the debug build the resulting asserts come almost immediately: |
The issue was originally reported in pinterf/mvtools#46: a very-very complex AviSynth script encoded with ffmpeg resulted in random freezes. The actual freeze is rare. It may occurs under very sensitive and hard-or-unable-to-reproduce timing conditions. E.g. lock-up happens after eight hours and many hundred thousand frames.
The text was updated successfully, but these errors were encountered: