Doom9's Forum - View Single Post - ffdshow tryouts project: Discussion & Development

Artofeel · 4th July 2016, 11:50

There is bug in AVIS "decoding" on 64bit
after ffdshow starts a new avisynth thread(?), it does not close the old one, which leads to memory leaks
this doesn't happen on the 32bit
to "visualize" problem, here a simple example script based on MP Pipeline

Code:

MP_Pipeline("""
### platform: win64
FFVideoSource("some.video")
### ###
""")

if you create avi dummy and opened it in x64 VirtualDub, press playback and start seeking on timeline, as a result you will see that every click will launch 'MP_Pipeline.dll.slave.exe' and the old one will not be closed
but in x32 VirtualDub, everything is fine, old copy of "MP_Pipeline.*.slave.exe" closes properly
it's not Avisynth bug, since if you change platform to 32 bit

Code:

### platform: win32

result will be same

I know that probably talking in the void, but maybe someone can fix this...

4th July 2016, 11:50	#15312 \| Link
Artofeel Registered User Join Date: Apr 2016 Posts: 8	There is bug in AVIS "decoding" on 64bit after ffdshow starts a new avisynth thread(?), it does not close the old one, which leads to memory leaks this doesn't happen on the 32bit to "visualize" problem, here a simple example script based on MP Pipeline Code: MP_Pipeline(""" ### platform: win64 FFVideoSource("some.video") ### ### """) if you create avi dummy and opened it in x64 VirtualDub, press playback and start seeking on timeline, as a result you will see that every click will launch 'MP_Pipeline.dll.slave.exe' and the old one will not be closed but in x32 VirtualDub, everything is fine, old copy of "MP_Pipeline.*.slave.exe" closes properly it's not Avisynth bug, since if you change platform to 32 bit Code: ### platform: win32 result will be same I know that probably talking in the void, but maybe someone can fix this...