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

Radian 0.6.13 crashes after calling reticulate. #489

Open
camsique opened this issue Sep 16, 2024 · 6 comments
Open

Radian 0.6.13 crashes after calling reticulate. #489

camsique opened this issue Sep 16, 2024 · 6 comments

Comments

@camsique
Copy link

radian --version
radian version: 0.6.13
r executable: /usr/local/lib64/R/bin/R
r version: 4.3.1
python executable: /usr/bin/python
python version: 3.9.18

Case 1) No crash, but does not work.

r$> library(reticulate)
r$> pd <- import("pandas")
Error: C stack usage  7973712 is too close to the limit

Case 2) Crashes

r$> library(reticulate)
r$> use_python("/usr/bin/python")
Error: C stack usage  7975088 is too close to the limit
Error: C stack usage  7974544 is too close to the limit

 *** caught segfault ***
address (nil), cause 'memory not mapped'
Segmentation fault (core dumped)

Case 3) No problem calling this in plain R console.

This used to work in radian prior to upgrading to development version.

@randy3k
Copy link
Owner

randy3k commented Sep 16, 2024

It seems that reticulate 1.39 introduces some changes that break how radian interacts with it.

Downgrading reticulate to 1.38 is a workaround for now before I have time to investigate the exact cause.

remotes::install_version("reticulate", version="1.38")

@randy3k
Copy link
Owner

randy3k commented Sep 16, 2024

At the first glace, it is most likely caused by rstudio/reticulate#1641 where it changes how the python is initialated.

@camsique
Copy link
Author

Dear randy3k, the workaround with reticulate downgrade works. Thank you. Also thank you for the amazing package!

@randy3k
Copy link
Owner

randy3k commented Sep 16, 2024

I have found the culprit and reported to upstream. Hopefully they will be able to fix it soon.

@camsique
Copy link
Author

Thank you.

@randy3k randy3k mentioned this issue Sep 21, 2024
@randy3k
Copy link
Owner

randy3k commented Sep 21, 2024

It should be fixed in the next reticulate release.

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