Automated Crash Reporting

RStudio allows you to automatically capture crash dumps for all RStudio processes and upload them to our crash database for easy reporting, allowing us to more easily determine the exact cause of crashes without adding administrative overhead to your team by requiring you to manually collect crash dumps. As user privacy is of utmost concern, these crash dumps only contain stack information, such as the names of the functions that were on the callstack at the time of the crash. No heap information is stored within the dumps, so no sensitive user data is captured in the crash dumps. The IP address of the machine uploading the reports is captured and used only to determine the unique amount of users experiencing a crash.

Crash Handler Configuration

A separate RStudio process is responsible for handling crashes, and may be configured similar to other RStudio processes by modifying the config file /etc/rstudio/crash-handler.conf. Automated crash handling is disabled by default, though we recommend that you enable it. The following shows a table of available configuration options for /etc/rstudio/crash-handler.conf:

Config Option Description Required (Y/N) Default Value
crash-handling-enabled Enables/disables automatic capturing of crash dumps for all RStudio processes. N 0 (disabled)
crash-db-path Location of the path where crash dumps should be stored on disk. This path must be readable and writable by all RStudio users. N /tmp/crashpad_database
uploads-enabled Enables/disables automatic uploading of crash dumps to our crash reporting service. If this is disabled, you will have to manually upload crash dumps. N 1 (enabled)
upload-url Web URL where crash reports are uploaded. You should likely not change this setting unless RStudio Support instructs you to do so. N
upload-proxy Proxy server to connect to when submitting the minidump. Only applicable on Linux - uses the default system-wide setting on OSX. If left blank, any system-wide setting specified will be used. This should be in the form of [scheme]://[host]:[port], where scheme may be one of the following: http https socks4 socks4a socks5 or socks5h. For more information, see N

For most RStudio installations, it is sufficient to merely set crash-handling-enabled=1 in the config file , like so:

# /etc/rstudio/crash-handler.conf

Manually Uploading Crash Dumps

In some cases, you may be unable to automatically upload crash dumps to the crash reporting service because of lack of internet connectivity or simply because you want to manually upload crash dumps. RStudio allows you to manually upload crash dumps at any time by invoking the following command:

rstudio-server upload-minidump /path/to/minidump

Locally Collecting Crash Dumps

In some environments it may not be possible to automatically upload crash dump or a crash dump may have been requested by RStudio Support to assist in investigating an issue. In these situations crash dumps can be collected locally. When locally collecting crash dumps inside a container, make sure that the crash-db-path is a directory that will persist outside of the container.

# /etc/rstudio/crash-handler.conf
crash-db-path=<some path>

The crash-db-path must be readable and writable by all RStudio Workbench users and processes. If shared storage is in use creating a crash-dumps subfolder below it may be a good option.

Crash dumps will be created in the <crash-db-path>/completed directory. Once one or more crash dumps have been recorded, the entire crash-db-path directory should be archived with a tool like tar or zip and provieded to RStudio Support for analysis.