ReSharper C++ Troubleshooting guide

If you encounter any issues, you're welcome to contact support or report to our public issue tracker. You can collect a specific dump file or logs to provide more details and help the team investigate the issue.

By default, the ReSharper log includes top-level entries of interactions between Visual Studio and ReSharper, as well as error messages from ReSharper core subsystems (ReSharper | Help | Show Log). For a more detailed log, switch the level of log messages to Verbose: How to run ReSharper with logging.

The team can also ask you to enable a trace scenario that will add exhaustive info about specific subsystem actions to the log, e.g. C++ Unit Testing: How to collect ReSharper log file with a specific trace scenario?

‘Cannot resolve symbol’ or ‘Cannot find file in search paths’

If you see red code in the editor but the project is compiled successfully: 

1. In the file with unresolved symbols or #include files, invoke Navigate->Go to Action.
2. Type /all Dump C++ inclusion context and press Enter.
3. Save the resulting dump file.

ReSharper features are not available in the file

If there are no ReSharper features available in some specific file, please try the following:

• If it is an external file, e.g. an included library header, try enabling Enable inspections, quick fixes, and context actions in files external to the solution on the Code Editing | C++ | General page of ReSharper options.
• If the file is large and exceeds the reasonable number of lines, check out the file health indicator just above the scroll bar. Usually, the icon shows the analysis status, but you'll see the pause sign instead. Right-click the icon and choose Resume analysis.
• If the file is generated or shared between the projects, and its content is missing in the navigation or completion results: 
  1. In the affected file, invoke Navigate->Go to Action.
  2. Type /all Dump Project Model and press Enter.
  3. Save the resulting dump file.

Code analysis misreads project properties

In general, ReSharper C++ relies on compilation properties reported by Visual Studio. However, depending on the configuration, you can sometimes face issues like inspections that do not match the specified C++ language standard version, or a C file treated like a C++ file.

1. In the affected file, invoke Navigate->Go to Action.
2. Type /all Dump C++ IntelliSense info and press Enter.
3. Save the resulting dump file.

Performance issues

ReSharper has bundled profilers to capture performance snapshots that allow us to find out what went wrong. If you notice any specific lagging actions, e.g. slow typing, please collect a Timeline snapshot: Collect Timeline performance snapshot in Visual Studio.

When Visual Studio is freezing, and it’s not possible to use embedded profilers, please collect a Timeline snapshot with a standalone dotTrace profiler: Profiling with standalone profilers.

Visual Studio crashes

If Visual Studio crashes only when ReSharper is enabled, please collect a crash dump as described in this article. Alternatively, add the registry settings to create a crash dump on each crash of Visual Studio automatically. You can run the enable_dump.reg file or add the following to the registry manually:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\devenv.exe]
"DumpFolder"="C:\CrashDumps"
"DumpCount"=dword:00000010
"DumpType"=dword:00000002

In that case, the dump will be collected in C:\CrashDumps. Then please share it via https://uploads.jetbrains.com/ and send us the Upload ID.