Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

How to debug Error: Session Closed. #3504

Unanswered
varna asked this question in Q&A
Discussion options

Hi,

Sometimes my tests fail with: Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.

 Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
 at CDPSession.send (node_modules/puppeteer/lib/Connection.js:180:29)
 at ExecutionContext._evaluateInternal (node_modules/puppeteer/lib/ExecutionContext.js:107:44)
 at ExecutionContext.evaluate (node_modules/puppeteer/lib/ExecutionContext.js:48:23)

If I run yarn test:e2e --steps --https --port=3000 --reporter mocha-multi --serve --verbose --full-memory-crash-report on a local machine, it feels like random crashes. My project is quite fat, but I have never seen it crash like that in dev or prod env. CI pipeline is quite flaky and each test has like 5% chance to fail with a such crash.

How do I debug these crashes?

You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /