Unfortunately I can't reproduce this easily, but I have a devtools bug
report (https://github.com/hadley/devtools/issues/885#issuecomment-137216148)
which appears to be because:
R.home("bin")
#> [1] C:/Program Files/R/R-32~1.0/bin/x64
even though on this computer "Program Files" is actually "Prog
On Wed, Sep 2, 2015 at 7:35 PM, arnaud gaboury wrote:
> After a few days of reading and headache, I finally gave a try at
> building R from source with Intel MKL and ICC. Documentation and posts
> on this topic are rather incomplete, sometime fantasist et do not give
> much explanations about conf
Well it'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-
After a few days of reading and headache, I finally gave a try at
building R from source with Intel MKL and ICC. Documentation and posts
on this topic are rather incomplete, sometime fantasist et do not give
much explanations about configure options.
As I am not sure if mine is correct, I would app
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
