Question:
Rider UI is completely unresponsive. How to collect frontend thread dumps for troubleshooting the freeze?
Answer:
Collect a thread dump using jstack utility if Rider does not respond to any actions for a long period of time:
- Open
{ide_installation_path}/jbr/binin a terminal. (MacOs path:{ide_installation_path}/Rider.app/Contents/jbr/Contents/Home/bin/); - Find the Process ID (
PID) of the "JetBrains Rider" process (rider64.exeorrider); Note: Either use OS processes monitor (Activity monitor/Task Manager) or get the PID from the.\jps.exe -lcommand output. The number next to thecom.intellij.idea.Mainis the PID of the Rider frontend process; - Invoke
.\jstack.exe -l {PID}>dumpN.txt(MacOs/Linux:./jstack -l {PID} > dumpN.txt) with N in 1..5; - Attach the generated
dump1..5.txtfiles to your issue or support ticket;
A dump should be taken exactly at the moment when the IDE is not responsive.
Note: If the IDE is responsive, see Rider is slow. Frontend performance snapshot
Comments
0 comments
Please sign in to leave a comment.