Rider frontend RAM issue. rider64 | rider process memory snapshot

Symptoms

Memory Leak or High Memory Consumption.

Question

How to collect frontend memory snapshot to investigate a particular memory leak or high memory consumption issue related to Rider frontend process?

Answer

If Rider uses a lot of RAM but does not crash

• Enable Memory indicator by right-clicking the status bar and selecting Memory Indicator.
• Reproduce the issue
• Verify that Rider uses a lot of memory according to the memory indicator
• Use Help | Diagnostic Tools | Capture Memory Snapshot
• IDE will prompt (in the bottom-right corner) the snapshot is generated, so that you can access it. If prompt is missing, see the Notifications tool window:

If Rider uses a lot of RAM and crashes with an "Out of memory" error

• Add the following line into .vmoptions file

-XX:+HeapDumpOnOutOfMemoryError

• Reproduce the issue
• The dump file will be created in the current working directory of Rider. In case this directory is read-only, set HeapDumpPath to change it to an arbitrary path

-XX:HeapDumpPath=/path/to/dump

Once you collect a snapshot, upload the snapshot via the Upload Service and mention the Upload ID in your issue or support ticket.

Please note that a memory snapshot may contain the sensitive information including parts of a source code from your project.