I agree with the above- after having to force kill Unity it works again to hit breakpoints, but only once. Then I have to kill it again =(

Happening to me as well. If anyone has discovered a fix, please post it here.

Just confirming that I have this issue as well.
Sometimes it works like a charm. Sometimes it crashes every single time I try to hit a breakpoint with Noesis relevant code.

Right now it's making me furious seeing unity crashing and freezing everytime, no matter where I put the breakpoint

Edit: When I put the breakpoint after a code block, like onto the closing brackets of a method, the breakpoint will be reached. But if I put it directly onto a line of code, Unity freezes.

Edit 2: Nevermind, it freezes anyway. This is getting really tough, I'm not able to debug right now.

We think we are in the right direction to fix this, we found a workaround to avoid this inconvenient Unity side effect.

Thanks everybody for being patient and please continue reporting in this thread about it.

That's good to hear. Looking forward to your updates!

Using vs2017 or Rider 2017.1 and Unity 5.6.3f1 have this issue too.

Are there any update news on this issue?

Great to hear you're working on the fix. Just posting I still see it with Rider and Unity 5.6.3.

We plan to release a 2.1 beta (only for windows) in the next 24 hours.

Is the new beta out yet? If yes, where can I find it?