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

segfault when using a fastmap to store data read using arrow #602

Open
dgkf opened this issue Feb 20, 2025 · 0 comments
Open

segfault when using a fastmap to store data read using arrow #602

dgkf opened this issue Feb 20, 2025 · 0 comments

Comments

@dgkf
Copy link
Contributor

dgkf commented Feb 20, 2025

I've been trying to chase down this bug for a while, and although I don't have a solution I've tried my best to pin down a reproducible example in a reprex over in dgkf/reprex-covr-segfault.

In short, a package that uses a pattern such as

function(f) {
  m <- fastmap::fastmap()  
  m$set("data", arrow::read_parquet(f))
}

will segfault when trying to calculate code coverage.

At it's core, it usually segfaults any time a package tries to store a arrow data.frame inside a fastmap stored somewhere within the package namespace.

I say usually because coverage will run to completion on the current CRAN release of covr if there is an if statement (and maybe others?) somewhere in the package code. I was only able to reliably test this by putting an if (TRUE) {} statement in the .onLoad function, but the behavior was rather sporadic and I think it's also affected by the presence/absence of S3 method registration. The development version of CRAN fails regardless.

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