Reprex when it makes R crash #312
Oct 28, 2020
Has there been a solution to this bug report? I am experiencing a similar issue. Am running R 4.0.3, and recently uninstall/reinstalled reprex to the latest version.
Jan 1, 2021
Notes from addressing this, because I had to settle for a compromise and I learned a few things I don't want to re-learn.
The ideal output would probably consist of:
I had to settle for just the latter. Given the current design, it would be very fiddly to get the ideal output and I don't think it's worth it.
I learned about
I did some manual tests with real crashes found by searching for
Some segfaults are caught in a way that does not lead to a crash and reprex doesn't work well for these, before or after this issue and PR. It seems to possibly be a
A real example where I encountered this is tidyverse/dplyr#5667.
Here's what I see in the R console for this, i.e. the R session survives:
And here's what happens when I
In this case, the
Jan 2, 2021
Happy new year! Many thanks for looking into this. Will try the dev version, but not sure I understand your last code block. Looking at the linked commit it seems that this is not the behaviour of the development version of reprex. Where does the
Jan 2, 2021
You will also not see the crash info or backtrace if you are on Windows, due to how R behaves and crashes on Windows. See r-lib/callr#178 for more.
I have some trouble generating the reprex of a process that ends up killing the R process. It makes Rstudio crash and hang up the bare R session (with core dumps).
The error I see is
I don't know if this could be handled different on the reprex side or on the callr side. I originally wrote the issue on callr r-lib/callr#143 but it seems it belongs here. There are some possible workarounds apparently.
I expected to get at least the same message that I see on the R session without RStudio.
The text was updated successfully, but these errors were encountered: