Start debugging from NCrunch inside Rider does not work most times

Hi,

Since plenty of months (or years), over several Rider and NCrunch Versions (Up to 2026.2 EAP) I have this problem.

Starting debugging

* From the Test Windows
* From Break into First Failing Test (and the likes)
* Do not know if they are more ways :)

Does not work most of the times not.

It seems that the Process Inside Rider is startet somehow, but the test did not finishes or reach the
the set breakpoint.

Starting Debugger via Rider itself works every time, but it is more work (setting breakpoint, searching the test, start the debugging of that test).

Am I alone with that?

Thanks for sharing this.

I haven't seen this problem myself. So there's a catch here. Could you submit a bug report after it fails? The report might yield some interesting clues.

A few more questions to help narrow this:
- Does the operation actually set a visible breakpoint?
- Can you describe the test run itself in more detail? Does the test show as running in the Processing Queue? Does it hang?
- If you try to do this 5 times, how many times out of the 5 does it fail?

Yes, break point will be set. When it fails it fails all the time, but i do not try 5 times in the row.

Will make a detailed report and description on monday when that Windows laptop will be switched on.

I've reproduced the issue now. Will see what I can do about fixing it. Thanks for the heads up.