Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught Error: Attempting to use a disconnected port object #28443

Closed
MaksuCode opened this issue Dec 1, 2023 · 6 comments
Closed

Uncaught Error: Attempting to use a disconnected port object #28443

MaksuCode opened this issue Dec 1, 2023 · 6 comments

Comments

@MaksuCode
Copy link

MaksuCode commented Dec 1, 2023

Current behavior

Problem : On Cypress UI, sometimes I have the problem that test cases fail to finish and run forever. It happens on a random basis.

Steps to reproduce :
1 - Open Cypress UI with browser Chrome 119
2 - Run a spec file

Actual result : Sometimes test cases fails to finish and runs forever due to the uncaught error that is mentioned below

Console log :

image

The breaking code block :

image

Desired behavior

The test cases should be executed properly.

Test code to reproduce

I will try to add it as soon as I could reproduce it on the forked repo.

Cypress Version

v13.6.0

Node version

v18.18.0

Operating System

Windows 23H2

Debug Logs

No response

Other

No response

@clewott
Copy link

clewott commented Dec 15, 2023

I am seeing this issue as well on 13.6.1.

@akselil
Copy link

akselil commented Feb 9, 2024

We have also this issue with Cypress 13.6.4

@jennifer-shehane
Copy link
Member

Could you all try to update to 13.6.6 and let us know if you're still experiencing this issue? We fixed an issue in 13.6.5 that was introduced in 13.6.0 and we want to understand if this has also resolved this issue. Thank you!

@jennifer-shehane jennifer-shehane added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: investigating Someone from Cypress is looking into this labels Feb 26, 2024
@MaksuCode
Copy link
Author

I am not facing this issue anymore with v13.12.0

@jennifer-shehane jennifer-shehane removed the stage: awaiting response Potential fix was proposed; awaiting response label Jul 1, 2024
@lukascivil
Copy link

I am facing this issue with v13.13.0 on macOS with chrome 126.

@jennifer-shehane
Copy link
Member

@lukascivil Please provide an example and way to reproduce in a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants