failures in headed tests randomly invoke debugger

[dwelle]

• Operating System: win7
• Cypress Version: 3.0.2

Is this a Feature or Bug?

bug

Current behavior:

Sometimes, particularly when the cypress runner browser is open for longer periods time, a failure (be it command/assertion failure, or some unhandled exception such as TypeError) causes a debugger to be invoked (i.e. it pauses the script execution).

Restarting the cypress browser window solves the issue (until it pops up again hour or sooner later -- I haven't figured out the pattern yet).

How to reproduce:

No idea.

I've registered a handler on fail event which does some things and then simply rethrows the error, but I believe the debugger thing happens even when the handler isn't registered, so I don't think it's related to this at all.

Just putting it here in case someone has an idea what's going on or encounters the same thing.

EDIT: to elaborate, the debugger is never being invoked until some point in time, and then from that point onward, it's being invoked 100% of the time (until I restart the browser window).

[brian-mann]

It's likely this setting in your dev tools

[dwelle]

@brian-mann nope, that's not it. That would not cause the behavior I'm getting -- it'd be consistent. So unless cypress (browser) is keeping that setting buried down somewhere in cache, and decides to use it as it pleases, I don't think that's what's happening.

[dwelle]

I'll close this for now. We'll see if some more people are getting this, or if it happens to be some quirk of my install.