Martin Gadbois wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Gadbois wrote:
Using OpenVPN 2.0.5 and 2.0.9, I notice that an somewhat idle connection
increases the RSS of the server process linearly with time.
Here is my patch to fix this issue. It does create (accordin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Gadbois wrote:
> Using OpenVPN 2.0.5 and 2.0.9, I notice that an somewhat idle connection
> increases the RSS of the server process linearly with time.
>
Here is my patch to fix this issue. It does create (according to
valgrind) a memory leak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marko Rauhamaa wrote:
> Martin Gadbois :
>
>> I've looked at the code (Yeah! Open Source) and could not see any
>> lists, or code that accumulates data, apart from gc_*().
>
> There's this weird scheme by which you prepare a memory pool with
> gc_new
Martin Gadbois :
> I've looked at the code (Yeah! Open Source) and could not see any
> lists, or code that accumulates data, apart from gc_*().
There's this weird scheme by which you prepare a memory pool with
gc_new(). Memory keeps on accumulating in the pool with alloc_buf_gc()
(in print_sockad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marko Rauhamaa wrote:
> You might be suffering from the problem I sent a patch for some months
> back. Basically, socket.c, socket_connect() accumulated unlimited
> amounts of memory if the server wasn't available. I added a pair of
> gc_free()/gc_new(
Martin Gadbois :
> Using OpenVPN 2.0.5 and 2.0.9, I notice that an somewhat idle connection
> increases the RSS of the server process linearly with time.
>
> valgrind says that there are no memory leaks. So where is this memory kept?
You might be suffering from the problem I sent a patch for som
