Hi Tim,

I've been trying to track down an issue which I suspect may be the same as this one.

Can you share any more detail on the nature of the freezes? How often do you get them, and how long do they show for? Do you sometimes have sessions that don't have them?

Also, can you confirm whether you enabled detailed logging to try and troubleshoot the freezing? I'm wondering if it still happens when Log Verbosity is set to Summary.

Hi Tim,

The 'Log to output window' setting doesn't work under Rider, as it doesn't have an output window like VS does for reporting log details.

When logging is enabled under Rider, the logs are written into the backend Rider logs. I noticed in the data you sent through that you have a lot of data landing in these logs, and I'm not sure how efficiently the Rider backend can process this. It may be implicated in the freezes. I think it's best if we first try to rule it out.

Could you try setting your Log Verbosity to Summary and see if this has any affect on the freezes?

At this stage, I'm not sure. It depends on whether the freeze is related to the vast amount of data being logged. If you can confirm whether changing the log verbosity has an effect, this will narrow the issue down somewhat.

Thanks for these extra details. I was wondering if I was the only one seeing this issue and that perhaps it was specific to my environment. I now know that is not the case.

There's a few things I've discovered about this problem in my efforts so far to resolve it:
- It's intermittent, and seems to happen regardless of the state of the NCrunch engine. Just by having NCrunch installed, it can happen
- It's originating from the Rider backend process. The problem appears when the main thread in Rider is waiting on the backend for something which seems to take a long time to appear
- There are no NCrunch stack traces directly implicated in the problem. When a debugger is attached to the backend process during a hang, there are no NCrunch threads that seem to be involved
- I seem to get sessions where the problem appears extremely often, enough to be infuriating. Then I get sessions where it never shows up at all. I have found it very hard to reproduce at will
- I suspected this might be caused by heap compactions but initial profiling results suggest they are not involved
- I haven't found log files to be any help here. Whatever is going wrong, the logs don't show it (neither NCrunch nor Rider)
- I really hate this problem

It's likely this needs to be solved deductively. Any patterns you can find to help narrow it down will really help me a lot.

Thanks for confirming this.



No, or at least, I don't think this specific problem is being caused by Copilot. I have seen it before without Copilot being loaded.

Can you tell me more about the setup your colleagues are running? Are they also using Rider? If so, are there any notable configuration differences between your machine and theirs?