-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[R] write_dataset gets a "zsh: illegal hardware instruction R" error #37034
Comments
We have had many reports of this error ( #36685 ), which primarily surfaces on the x86 flavour of R running on MacOS M1. I believe a fix has been merged; however, it won't be released for a few months (it's slated for 14.0.0). A few workarounds:
|
I would be curious if the |
@paleolimbot thanks for this suggestion, I added to my zshrc file, made sure zsh is my default shell/confirmed the env var, restarted, tried and still got the error, though it added this number, perhaps the process id, not sure.
|
) Resolves #33807 and #37034 ### Rationale for this change If someone is running R under emulation, arrow segfaults without error. We can detect this when we load so can also warn people that this is not recommended. Though the version of R being run is not directly an arrow issue, arrow fails very quickly in this configuration. ### What changes are included in this PR? Detect when running under rosetta (on macOS only) and warn when the library is attached ### Are these changes tested? No, given the paucity of ARM-based mac CI, testing this organically would be difficult. But the logic is straightforward. ### Are there any user-facing changes? Yes, a warning when someone loads arrow under emulation. * Closes: #33807 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jonathan Keane <[email protected]>
From what others have reported, I'm not sure changing variables will get this to work assuming you're running an Intel version of R on a non-Intel mac. With other similar issues like this, it's been resolved by installing a native (arm64) build of R. Assuming the above is correct, I'm going to close this issue, but feel free to reopen if it's not the case and we can discuss more! |
apache#37777) Resolves apache#33807 and apache#37034 ### Rationale for this change If someone is running R under emulation, arrow segfaults without error. We can detect this when we load so can also warn people that this is not recommended. Though the version of R being run is not directly an arrow issue, arrow fails very quickly in this configuration. ### What changes are included in this PR? Detect when running under rosetta (on macOS only) and warn when the library is attached ### Are these changes tested? No, given the paucity of ARM-based mac CI, testing this organically would be difficult. But the logic is straightforward. ### Are there any user-facing changes? Yes, a warning when someone loads arrow under emulation. * Closes: apache#33807 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jonathan Keane <[email protected]>
apache#37777) Resolves apache#33807 and apache#37034 If someone is running R under emulation, arrow segfaults without error. We can detect this when we load so can also warn people that this is not recommended. Though the version of R being run is not directly an arrow issue, arrow fails very quickly in this configuration. Detect when running under rosetta (on macOS only) and warn when the library is attached No, given the paucity of ARM-based mac CI, testing this organically would be difficult. But the logic is straightforward. Yes, a warning when someone loads arrow under emulation. * Closes: apache#33807 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jonathan Keane <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
Hi - we use arrow in R and python for a wide range of projects at my company but are running into a datset issue with R-arrow I am not sure how to track down, it may be something with my system. Recently updated to 12.0.1.1 on an M1 Max x86 running on Ventura 13.4
Running the following I'm able to read/write parquet file no problem:
But trying to write a dataset I get an immediate "Fatal Error" crash in Rstudio. Running in R, This happens:
I get what appears to be a prompt asking me to make a Selection (see image), with no options. I just put in "1" and get the
zsh: illegal hardware instruction R
error`Tracing the error i made it to
Schema__WithMetadata()
before it broke.Some context:
open_dataset
also has the same result on some preexisting datasets we've created at my company, this is actually where I came across the error and then foundwrite_dataset
was doing something similar.I dont know why sessionInfo says Im running under Big Sur/Monterrey below, maybe that has something to do with it? My company has software manager (kandji) and updated this mac to Ventura a while ago. Could just be me :/
I have no problems running this test script on my other mac, which is an Mac Pro Intel chip on Ventura 13.5. Others have had no issue but they're all Intel. We all run on the same
renv
project.ran
brew install apache-arrow
as well, which updated/installed12.0.1_4
, but my understanding is the mac binary for R-arrow comes with everything, I assume that version wouldnt be an issue anyway but could there be confusion there?Component(s)
R
The text was updated successfully, but these errors were encountered: