[x264-devel] libx264 memory leak

[Sean McGovern]

How...is that OS specific? Are #ifdef's really that hard, Loren?
-----Original Message-----
From: Loren Merritt <lorenm at u.washington.edu>

Date: Tue, 3 Mar 2009 21:28:41 
To: Mailing list for x264 developers<x264-devel at videolan.org>
Subject: Re: [x264-devel] libx264 memory leak


On Tue, 3 Mar 2009, Leon Woestenberg wrote:
>
> Under Unices, using a library constructor/destructor approach is available:
>
> http://www.faqs.org/docs/Linux-HOWTO/Program-Library-HOWTO.html#INIT-AND-CLEANUP
>
> Not sure how Windows handles that though,

No way am I using a OS-specific feature for this. If shutting up valgrind 
is really important, just put it in a static array.

--Loren Merritt
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel