Today I got this error, and I just did a small workaround which was too simple.
You will not get the error again and if the debugger doesn't hit, refresh the browser again.
Update (12-Dec-2018):
I just tested this bug in Visual Studio 2019 preview, it seems like the bug is fixed now.
Hope this helps.