Anyone else has strange lockup issues?

[osgZach]

I don't know exactly when this started, or what the cause might be, but I have had weird issues where Vdub hardlocks and does not respond when working with Avisynth scripts in particular.

It seems to be able to load various supported formats directly and function normal except for when I feed it an AVS script and try to hit play it'll freeze up on me. Controls unresponsive, etc. It'll even affect render outputs where the job finishes fine, but for whatever reason does not end, just hangs there on the final frame, etc.

I tried backpeddling to 1.9.11 and while the script starts and continues to play, the controls and program itself still freeze up and I have to kill it manually.

This issue only seems to occur with AVS scripts. Even on Vanilla unzip of Vdub package with nothing installed.


Are there any tools which can thoroughly clean out / reset the underlying VFW and other systems to as close a "default" install state as possible? That's one avenue I might like to try pursuing

I'm planning on a reinstall soon (been going on 3 - 4 years without a wipe) but I'm nowhere near ready and have loads of files and data to sort through/backup before I am able to test from a truly clean system.

[shekh]

Not sure if it is related to your problem, but I sometimes experience UI unresponsiveness. For example I hit play and cannot stop it or do anything until it runs completely to the end. I suspect in my case this happens because something like decoder is high priority and eats all cpu cores completely, but I didnt attempt to look closer yet.

[osgZach]

Yeah that sounds very familiar.

[StainlessS]

Clear out your plugins directories for both Avisynth and VirtualDub, use only the plugins that you require, does it work now ?
If so, then try adding back the plugins in batches until problem re-appears, remove/add from the last batch until culprit plugin found.

[osgZach]

Yeah I tried that. It's very strange. But it does seem related to Avisynth I think. I'm doing a full format soon (maybe tonight or tomorrow) once I'm done backing stuff up.
On my other PC which is very minimal it doesn't appear to have problems in the limited quick testing I did. Reverting back to 2.58 didn't seem to make a difference

This Windows install is nearly 4 years old now so that may have something to do with it.

[raffriff42]

Nonlinear access (including temporal filtering) with a decoder that doesn't do random seek very well, maybe?
Sometimes it pays to make a lossless, intra-only working dub before applying a complex script.

There's an off chance the preview rendering is to blame. Options, Preferences, Display, disable acceleration.

[osgZach]

Yeah been through those kinds of options. I'm literally getting preview lockups with nothing but a AviSource() script.

Will see how it goes after the format I guess :)

[shekh]

Btw, what input plugins you have installed?

[osgZach]

Well right now I have a fresh Windows 7 install going, with vanilla Vdub 1.10 / AVS 2.6 RC3

So far it'll load and play a basic script without locking up. So guess it'll be trial and error if I run into this problem again

[Emulgator]

Maybe Focus loss ? Infamous Win7 behaviour on my Win7 systems too.
Having to hit certain keys/switches repeatedly and/or unresponsive windows.
Some can be cured by "Run as administrator" for all users.

[shekh]

Not sure if it is related to your problem, but I sometimes experience UI unresponsiveness. For example I hit play and cannot stop it or do anything until it runs completely to the end. I suspect in my case this happens because something like decoder is high priority and eats all cpu cores completely, but I didnt attempt to look closer yet.

Eventually I attempted to analyze that problem
It seems isolated to VirtualDub display system, but I dont completely understand it. Anyway I made meaningful workaround in recent FilterMod build.