search for: corolari

Thanks, Tomas, Luke, for the clarifications. Then, I have another question. But first, let me introduce how I ended up here, because obviously I just don't go around dyn.unloading things that I've just compiled. I was testing a package with valgrind. Everything ok, no leaks. Great. But I'm always suspicious (probably unjustifiably) of all the memory that is reported as "still

Hi I?aki, I think that "still reachable" memory is potentially a problem only if you cared about (frequent) package unloading, and if package unloading did not have correctness problems in the first place. I would only worry about "memory leaks" reported by valgrind. That your example (unloading a library while there is still an object with a finalizer implemented in that

On 9 August 2018 at 20:37, Tomas Kalibera wrote: | So to answer your original question, this could probably be handled in | Rcpp, Hm. Why do you say that / what did you have in mind? Recall that we do not alter SEXPs or introduce additional additional reference counters -- because we do not think that altering the basic R API for such calls would be a wise strategy. So we do more or less what