thisisnic commented on issue #50466: URL: https://github.com/apache/arrow/issues/50466#issuecomment-4963193034
Thanks for reporting this @eligriv75! One thing that could help us get to the bottom of this is a stack trace on that crash. If you're able to install [WinDbg](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/), we could use that. I generated some instructions, show below. 1. Install [WinDbg](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/) from the Microsoft Store (or via winget install Microsoft.WinDbg). 2. Start RStudio and load your packages as usual, stopping just before the write_parquet() call. 3. In WinDbg: File → Attach to process → select rsession.exe (there may be more than one — pick the one whose start time matches your session, or close other RStudio windows first). 4. Once attached, the process will be paused — press g (or click Go/Continue) to let it run again. 5. Back in RStudio, run the write_parquet() call to trigger the crash. WinDbg should break in automatically. 6. In the WinDbg command window, run k (or ~*k for all threads) and paste the output here, along with the exception line WinDbg prints when it breaks (e.g. an access violation code). Also, out of interest, does running `options(arrow.use_threads = FALSE)` before `write_parquet()` change anything? -- 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]
