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
Valgrind sees a small leak #8
Comments
Looks like this goes away when we just remove the (redundant, as Rcpp's I see a residual error from |
The residual leak reported from e.g. a simple call
|
Turns out that upgrading to the current state (i.e. 'dev' 0.14.3 as at its repo) of
More work to do ... PS And while Writing R Extensions muses that the 'unconditional jump' may be from compiler optimzations and suggests building without optimizations, doing so (as a test) for both |
I'll reopen as while #9 is in and does not hurt, it did nuttin' on the valgrind issue. |
I have tracked down the lines that cause the issue:
To create the error, the setkey has to be there. I then get what you were getting in your first attempt (I'm running data.table 1.14.8):
By not using the
The above gives:
Will take an in-depth look at the |
We appear to have forgotten to close this. |
Thanks to a heads-up by Ivan on the r-package-devel list, we actually have an open issue with valgrind I was unaware of:
https://www.stats.ox.ac.uk/pub/bdr/memtests/valgrind/dtts/tests/tinytest.Rout
Time permitting, I will try to drill down a little and see if I can isolate it.
The text was updated successfully, but these errors were encountered: