RStudio Backtrace Utility


Note: The backtrace utility is only available on Linux for builds of RStudio Desktop v0.94.73 or later (currently unavailable on Fedora). For a crash on Mac OS X, you can look for a crash report.

If you experience a reproducible crash while running RStudio on Linux, you can run the built-in backtrace utility to help pinpoint the source of the crash. This backtrace will capture your stack traces, or a list of all the function calls up to the point of the crash, and give us a good indication of what went wrong.

Running the backtrace utility:

Note: This utility will install gdb (if it isn't already installed) and temporarily alter the system core pattern (so it can capture cores from multiple processes) -- for both of these operations sudo privileges are required and the script will prompt for sudo as necessary.
  1. Quit any existing instances of RStudio
  2. Run the following command from the terminal:

    $ /usr/lib/rstudio/bin/

  3. RStudio will launch automatically and you should now reproduce the crash

  4. After crashing, a rstudio-backtrace.txt file is written to the same directory as the backtrace script was launched.

  5. Send the rstudio-backtrace.txt file back to us at RStudio

This rstudio-backtrace.txt file contains the stack traces of the processes at the time they crashed. This will help show us where RStudio is crashing and ideally allow us to implement a fix.