[StainlessS]

Originally Posted by pinterf

Maybe it's not the frames but the string resources that will never get freed up. Shorten everything in the runtime section and see if it crashes later.

There are no strings used during Frame Serving stage, and the MI (Multi-Instance) template used above works flawlessly in all other MI functions that I've coded, I think is purely down to the single frame accumulator 'hanging on' to all previous frames used in the overlaying bit.
The MI stuff, usually poses no problem (no major problem) in functions using quite a few locally created strings during frame serving, but I usually make most of those (eg formatting strings for RT_Subtitle or similar), accessible via constant variables.

The MI interface created primarily by Martin53 & Gavino works extremely well.

EDIT: Actually, this MI function is way simpler than a lot of MI functions that I've done, using lots of string allocations (and they proved no problem less than maybe 500,000 or more frames).

EDIT:
On WXP32 4GB Ram, with Task Manager Open, opening script into VDub FilterMod,

where all strings already created and VDub displaying frame 0.

Physical Memory (K)
    Total        3405284
    Available    2944132
    System Cache 1047929

Page File Usage 512 MB

Moving to frame 1,

Physical Memory (K)
    Total        3405284
    Available    2939632
    System Cache 1048304

Page File Usage 515 MB