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

Memory issue observed on CRAN #6513

Closed
mattfidler opened this issue Sep 20, 2024 · 1 comment
Closed

Memory issue observed on CRAN #6513

mattfidler opened this issue Sep 20, 2024 · 1 comment

Comments

@mattfidler
Copy link

https://www.stats.ox.ac.uk/pub/bdr/memtests/valgrind/rxode2/tests/testthat.Rout

The offending code is here:

==1579489== Conditional jump or move depends on uninitialised value(s)
==1579489==    at 0x171DBA42: range_i32 (/tmp/RtmpcKmiav/R.INSTALL11a1932f6cfebb/data.table/src/forder.c:156)
==1579489==    by 0x171DBA42: forder (/tmp/RtmpcKmiav/R.INSTALL11a1932f6cfebb/data.table/src/forder.c:552)
==1579489==    by 0x171DE927: forderReuseSorting (/tmp/RtmpcKmiav/R.INSTALL11a1932f6cfebb/data.table/src/forder.c:1741)

I didn't see this posted anywhere so I posted this for your awareness. I will be replying to CRAN that I have raised this issue when I resubmit.

nlmixr2/rxode2#795

In general I am following the suggestion by @MichaelChirico here and is found in my repo here

Unfortunately CRAN's valgrind environment has always been a mystery to me. I did not see the issues on my end when I ran valgrind.

@mattfidler
Copy link
Author

I found the issue. Thank you for your patience with my spam.

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

1 participant