Textsub causes 100% cpu

[foxyshadis]

Anyone else having this problem? This is the first time I've used vsfilter since I got the new computer (core duo, xp pro).

Specifically, what happens is that when I load vdub with a single textsub call, it runs fine but hogging 50% cpu (one core) from the main system. Any more calls and it's 100%. Reloading hangs up vdub completely. Strange part is, if I use process explorer, I see extra vsfilter threads, one for each textsub, sitting there, and if I kill them cpu usage goes down to normal with no ill effect (subtitles work), except that reloads still hang.

I've tried versions of avisynth from 2.5.5 to current cvs, and the latest and an older vsfilter, and they ALL seem to do this. Also the last 3 versions of vdub, and mpc. It happens with any kind of source call, even blankclip(). These exact same subtitle files worked on my two old machines.

Anyone know why vsfilter sits in a busy loop like that?

[Daodan]

I don't know if my problem is the same as yours but I got this problem at playback. If I had external subtitles (ass or srt) I got max cpu (3200+), only if I had other subtitles (with different names in the same directory). Strange thing is that in the vsfilter menu only one subtitle was listed (I didn't check the processes though). Another strange thing is that if I embedded the ass in the mkv I get no more problems (still the same subs in the directory). So basically vsfilter is not bugfree.