Displaying 2 results from an estimated 2 matches for "td4710367".
2015 Sep 02
0
mclapply memory leak?
...'s only a leak if you don't get the memory back after it returns,
right?
Anyway, one (untested by me) possibility is the copying of memory pages
when the garbage collector touches objects, as pointed out by Radford Neal
here:
http://r.789695.n4.nabble.com/Re-R-devel-Digest-Vol-149-Issue-22-td4710367.html
If so, I don't think this would be easily avoidable, but there may be
mitigation strategies.
~G
On Wed, Sep 2, 2015 at 10:12 AM, Toby Hocking <tdhock5 at gmail.com> wrote:
> Dear R-devel,
>
> I am running mclapply with many iterations over a function that modifies
> n...
2015 Sep 02
4
mclapply memory leak?
Dear R-devel,
I am running mclapply with many iterations over a function that modifies
nothing and makes no copies of anything. It is taking up a lot of memory,
so it seems to me like this is a bug. Should I post this to
bugs.r-project.org?
A minimal reproducible example can be obtained by first starting a memory
monitoring program such as htop, and then executing the following code
while