If a part of the code is highlighted incorrectly, for example, one part is in one colour and another part is in another colour, additional debugging information is necessary.
Question
How to collect additional diagnostic information for troubleshooting if highlighting misbehaves in Rider, e.g.:
Answer
Enable Internal Mode.
Open the file with highlighting issues in the Editor and make sure it is in focus.
Go to Tools | Internal Actions | Markup actions | Dump All Highlighters:
The dump file will open in the Editor automatically.
Right-click the dump file name in the Editor, select Open In | Explorer (Windows) or Open In | Finder (macOS):
Perform steps 2-5 to collect Tools > Internal Actions > Markup actions > Dump Backend Highlighters in addition.
Find the
DumpAllHighlighters{TimeStamp}.txtandDumpBackendHighlighters{TimeStamp}.txtin the file system (see step 5);In addiction collect IDE logs via Help | Collect Logs and Diagnostic Data;
Attach two
.txtdumps and the generated logs bundle to your support request/YouTrack ticket.
Alternatively, upload dumps and logs to JetBrains Uploads service and share the Upload ID in the support request/YouTrack ticket.
Additional Information
A highlighting dump generates for the file that is currently focused in the editor. If the issue is present in the exact file, this file should be focused in the Editor prior to collecting the dump.
If the highlighting does not work at all - there is no any meaningful highlighting, collect logs with the Daemon trace scenario as instructed in How to collect Rider logs with Traces.
Comments
0 comments
Please sign in to leave a comment.