-
Notifications
You must be signed in to change notification settings - Fork 4.1k
[R] segfault on calls to arrow::S3FileSystem$create #30208
Copy link
Copy link
Closed
Description
I was trying out a colleague's example code today and ended up with a segfault. Their code was:
library(arrow)
minio <- S3FileSystem$create(
access_key = "",
secret_key = "",
scheme = "http",
endpoint_override = "data.ecoforecast.org"
)Though I'm able to reproduce the segfault with a more minimal example like:
library(arrow)
S3FileSystem$create()The output I get immediately in the R console is:
> S3FileSystem$create()
*** caught segfault ***
address 0x1a0, cause 'memory not mapped'
Traceback:
1: (function (anonymous, access_key, secret_key, session_token, role_arn, session_name, external_id, load_frequency, region, endpoint_override, scheme, background_writes) { .Call(`_arrow_fs___S3FileSystem__create`, anonymous, access_key, secret_key, session_token, role_arn, session_name, external_id, load_frequency, region, endpoint_override, scheme, background_writes)})(access_key = "", secret_key = "", session_token = "", role_arn = "", session_name = "", external_id = "", load_frequency = 900L, region = "", endpoint_override = "", scheme = "", background_writes = TRUE, anonymous = FALSE)
2: exec(fs___S3FileSystem__create, !!!args)
3: S3FileSystem$create()I've attached detailed info about my environment and a full core dump to the issue but the high level stuff is:
-
OS: macOS 12.0.1
-
R: 4.1.2
-
R arrow version: 6.0.0.2
Reporter: Bryce Mecum / @amoeba
Assignee: Jonathan Keane / @jonkeane
Original Issue Attachments:
PRs and other links:
Note: This issue was originally created as ARROW-14667. Please see the migration documentation for further details.
Reactions are currently unavailable