wechaty/puppet-whatsapp

Session closed. Most likely the page has been closed.

Open

#237 opened on Feb 17, 2022

View on GitHub
 (2 comments) (0 reactions) (1 assignee)TypeScript (23 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (26 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

22:30:00 ERR Config ###########################
22:30:00 ERR Config unhandledRejection: Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
    at CDPSession.send (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:218:35)
    at ExecutionContext._evaluateInternal (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:204:50)
    at ExecutionContext.evaluate (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:27)
    at DOMWorld.evaluate (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:95:24) [object Promise]
22:30:00 ERR Config ###########################
22:30:00 ERR Config ###########################
22:30:00 ERR Config unhandledRejection: Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed. [object Promise]
22:30:00 ERR Config ###########################
22:30:00 ERR Config process.on(unhandledRejection) promise.catch(Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.)
Config Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
    at CDPSession.send (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:218:35)
    at ExecutionContext._evaluateInternal (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:204:50)
    at ExecutionContext.evaluate (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:27)
    at DOMWorld.evaluate (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:95:24)
22:30:00 ERR Config process.on(unhandledRejection) promise.catch(Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.)
Config Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
    at CDPSession.send (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:218:35)
    at ExecutionContext._evaluateInternal (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:204:50)
    at ExecutionContext.evaluate (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:27)
    at DOMWorld.evaluate (/xiaoju-bot/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:95:24)
(node:10) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 28)
22:30:01 INFO BotAction syncContact(ready=false, forceSync=false)

Contributor guide

Research direction
Investigate premature page closure in puppeteer; ensure proper session cleanup and error handling.
Tech stack
typescriptnodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
puppeteerNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65