search for: l636

Displaying 3 results from an estimated 3 matches for "l636".

Did you mean: 636
2016 Nov 13
1
Memory leak with tons of closed connections
...pecial and R opens it with fdopen(): > https://github.com/wch/r-source/blob/f8cdadb769561970cc42776f563043ea5e12fe05/src/main/connections.c#L561-L579 > > and then it does not close it: > https://github.com/wch/r-source/blob/f8cdadb769561970cc42776f563043ea5e12fe05/src/main/connections.c#L636 > > I understand that R cannot fclose the FILE*, because that would also > close the file descriptor, but anyway, this causes a memory leak. I > think. > > It seems that you cannot close the FILE* without closing the > descriptor, so maybe a workaround would be to keep one FILE...
2016 Nov 11
2
Memory leak with tons of closed connections
On Fri, Nov 11, 2016 at 12:08 PM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Gergely Dar?czi <daroczig at rapporter.net> >>>>>> on Thu, 10 Nov 2016 16:48:12 +0100 writes: > > > Dear All, > > I'm developing an R application running inside of a Java daemon on > > multiple threads, and
2016 Nov 11
0
Memory leak with tons of closed connections
...#39;stdin' is special and R opens it with fdopen(): https://github.com/wch/r-source/blob/f8cdadb769561970cc42776f563043ea5e12fe05/src/main/connections.c#L561-L579 and then it does not close it: https://github.com/wch/r-source/blob/f8cdadb769561970cc42776f563043ea5e12fe05/src/main/connections.c#L636 I understand that R cannot fclose the FILE*, because that would also close the file descriptor, but anyway, this causes a memory leak. I think. It seems that you cannot close the FILE* without closing the descriptor, so maybe a workaround would be to keep one FILE* open, instead of calling fdopen...