[Helix-producer-issues] [Bug 15310] New: Large memory leak w/DS File reader using Avisynth as input
Helix Bug Tracker <[email protected]> Sun, 18 Nov 2012 19:34:51 -0800
| Newsgroups | gmane.comp.multimedia.helix.devel |
|---|---|
| Message-ID | <[email protected]> |
https://bugs.helixcommunity.org/show_bug.cgi?id=15310
guest created:
Priority: P3
CC: karll, sirber
Operating System: WinXP
AssignedTo: skharkar
QAContact: produceriz
Summary: Large memory leak w/DS File reader using Avisynth as inp
ut
Severity: S2
Status: NEW
Last changed date: 2005-06-27 14:11:48
Hardware: x86
Version: unspecified
Tracker: File Input
Project: helix-producer
Target Milestone: NextRelease
lyoung imported this issue from https://producerapps.helixcommunity.org/issues/show_bug.cgi?id=144
Issue state when exported:
AssignedTo: lyoung
Component: producerapps
creation_ts: 2003-03-03 13:13
Last changed date: 20030313152248
Issue #: 144
Status: NEW
Issue type: DEFECT
Keywords:
OS/Version: WinXP
Priority: P3
QAContact: issues@producerapps
Platform: x86
ReportedBy: karll
Resolution:
Summary: memory leak with Avisynth
Status Whiteboard:
Subcomponent: File Input
Target Milestone: Producer 9.2 beta
Version: current
Votes:
------- Additional Comments From [email protected] 2003-03-03 13:13 PST -------
I noticed that when I use an AVISynth script as
input to producer for 2-pass encoding, memory
usage almost doubles during the 2nd pass, even
though producer completely shuts down the
DirectShow reader before starting the 2nd pass.
So I ran another test, where I asked producer to
encode a directory with five AVS files. Producer
will then batch encode all the files in the
directory individually. What happened was that for
the last file,
producer's memory use was at 300 MB!
I have seen this with many previous versions of
AVISynth, but this specific example is with 2.5.
Could it be something about how producer shuts
down the DirectShow reader, or a problem with how
DirectShow interacts with AVISynth? The reason I
ask this, is because doing a 2-pass XviD encode in
VirtualDub with the exact same AVS input, memory
usage does /not/ increase.
My AVS scripts generally look something like
LoadPlugin
("C:\MISC\DVDTools\x2real\bin\avisynth\mpeg2dec\mpeg2dec.dll")
stream=MPEG2Source("L:\source.d2v")
audiofile=WAVSource("L:\source.wav")
stream=AudioDub(stream,audiofile)
stream=BilinearResize(stream,720,480)
stream=Trim(stream,0,2000)
return(stream)
------- Additional Comments From [email protected] 2003-03-13 15:22 PST -------
I did some work on this issue with AviSynth source code to aid
debugging, and found indications that the problem lies somewhere in
producer.
See http://forum.doom9.org/showthread.php?s=&threadid=47893
for all the details. Have not looked into producer's dsreader.
It is not possible to use producer's AVI reader can not be used for
.avs files to check if this has a memory leak, since producer's AVI
reader does not use Windows AVI interface, which is required for
AviSynth to work correctly. The reason producer has its own AVI reader
and parser is to be able to read uncompressed AVIs on Linux and OS X.
------- Additional Comments From guest 2012-18-11 19:34 GMT-0800 -------
This bug is a clone of bug #148, created by guest
--
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are in the CC list for the product the bug is within.
This e-mail is sent to you automatically from the Helix Bug Tracker. Please, do
not respond to this message, but instead edit your Bug Tracker user preferences
to change when Bug Tracker sends you e-mail.