Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Garbage collection issues #693

Closed
Enchufa2 opened this issue May 15, 2017 · 3 comments
Closed

Garbage collection issues #693

Enchufa2 opened this issue May 15, 2017 · 3 comments

Comments

@Enchufa2
Copy link
Member

Initially, I reported this in tidyverse/magrittr#146 (see the reprex there, please). But after many attempts, I'm definitely unable to take Rcpp out of the equation, and I'm starting to think that the issue has something to do with it. I cross-post here so that the Rcpp gurus can take a look.

@eddelbuettel
Copy link
Member

eddelbuettel commented May 15, 2017

I will close this as there is absolutely nothing reproducible here.

And an reprex with a pipe is not minimal.

@Enchufa2
Copy link
Member Author

I know, I know... but this is the best I managed to do so far. Do you know if it is possible that a reference to an environment is still visible to the gc but not to ls, and where?

@eddelbuettel
Copy link
Member

eddelbuettel commented May 15, 2017

You need to talk to the folks who deal in pipes, and standard vs non-standard evaluation. We "just" have C++ code here that very much guarantees you that an destructor is executed (but in our context maybe only once gc() happens). What we do is more straightforward. The other one is ... harder.

I would imagine you might be able to construct something without Rcpp exhibiting the same behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants