[GitHub] [arrow] paleolimbot opened a new issue, #37576: [R] Failed allocations call into R from a non-R thread

["paleolimbot (via GitHub)" <gi...@apache.org>]

paleolimbot opened a new issue, #37576:
URL: https://github.com/apache/arrow/issues/37576

   ### Describe the bug, including details regarding any error messages, version, and platform.
   
   The `gc_memory_pool()` is the one we use almost everywhere in the R package. It uses a special allocation mechanism that calls into R to run the garbage collector after a failed allocation (in case there are any large objects that can be removed). In the case where an allocation happens on another thread (most of the time when running exec plans), the call into R may cause a crash: even though the memory pool was ensuring serialized access using a mutex, this is not sufficient for R and this sort of code normally crashes R or leads to confusing errors.
   
   ### Component(s)
   
   R


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow] paleolimbot closed issue #37576: [R] Failed allocations call into R from a non-R thread

["paleolimbot (via GitHub)" <gi...@apache.org>]

paleolimbot closed issue #37576: [R] Failed allocations call into R from a non-R thread
URL: https://github.com/apache/arrow/issues/37576


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org