-
Notifications
You must be signed in to change notification settings - Fork 1.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
C stack usage is too close to the limit
with an Arrow source and parallelism
#2100
Comments
This is odd but probably something benign. |
Ha, I just came across this on #2077 |
Should be fixed by #2077 |
I'm getting this same error with The error tends to happen at random though, half of the times the query succeeds, and half of the times it tries to allocate several GB on the stack. |
We first noticed this in Arrow's CI after merging our DuckDB integration with
Error: INTERNAL Error: Failed to eval R expression Error: C stack usage 768360237712 is too close to the limit
.I've since been able to reproduce this locally on my Mac as well (6 core, 12 threads intel):
This happens when using the Arrow wrapper
to_duckdb()
as well, but was able to reproduce it usingduckdb_refister_arrow
directly so I don't think there's anything going on in the wrapper that is causing it.I also tried creating a fully instantiated table with
DBI::dbWriteTable(con, "mtcars_table", mtcars)
and that works just fine with the same queries, so it looks like it's something related to the registered source that's causing this to pop up.The text was updated successfully, but these errors were encountered: