thisisnic commented on issue #11665: URL: https://github.com/apache/arrow/issues/11665#issuecomment-971428232
In addition to `pitrou`'s comment on retrying `arrow::write_feather()` and checking the CPU activity, if you like, you could generate more diagnostic information by running the code with the C++ debugger attached. If you want to do this, there are some instructions in the dev version of the docs (https://ursalabs.org/arrow-r-nightly/articles/developers/debugging.html) but here's a short version: 1. Start up R in a terminal with the debugger using either `R -d gdb` or `R -d lldb` - hopefully one of these should work with your OS 2. Type `run` to run R 3. Run the code you run which causes the session to hang At this point, there should either be a load of extra output detailing the cause of the problem or the session will just hang again. If it just hangs, press Crtl+C to stop the debugger and then type in `thread apply all bt` - this will generate a tonne of output but it'll be really useful stuff for us! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
