[GH-ISSUE #230] Bug Report: Execution context was destroyed when syncing profile pictures in Docker setup #70

New issue

Closed

opened 2026-02-27 04:59:01 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 04:59:01 +03:00

Owner

Originally created by @robin-vandaele on GitHub (Oct 7, 2025).
Original GitHub issue: https://github.com/guyzyl/whatsapp-contact-sync/issues/230

Description
When running the app via the Docker variant, the sync process intermittently crashes with a Puppeteer error:

Code
Error: Execution context was destroyed, most likely because of a navigation.
at rewriteError (/app/server/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:284:15)
at async Client.getProfilePicUrl (/app/server/node_modules/whatsapp-web.js/src/Client.js:1503:28)
This happens during the profile picture sync (getProfilePicUrl), causing the backend to stop responding.

🌍 Environment
Deployment: Docker (combined backend + frontend image)

Host OS: Linux (x86_64)

✅ Steps to Reproduce
Build and run the Docker image as described in the README:

bash
docker build -t whasync .
docker run --rm -it -p 80:80 whasync
Open the web UI, scan the QR code with WhatsApp, and connect Google account.

Start a sync with options manual_sync=false and overwrite_photos=true.

After a few seconds, the backend crashes with the above error.

🤔 Expected Behavior
The sync should complete successfully, updating Google Contacts with WhatsApp profile pictures.

Puppeteer should remain stable during the entire sync process.

❌ Actual Behavior
The backend throws Execution context was destroyed during getProfilePicUrl.

Sync stops prematurely, and the container needs to be restarted.

📜 Relevant Logs
Code
/app/server/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:284
throw new Error('Execution context was destroyed, most likely because of a navigation.');
^

Error: Execution context was destroyed, most likely because of a navigation.
at rewriteError (/app/server/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:284:15)
at async ExecutionContext._ExecutionContext_evaluate (...)
at async Client.getProfilePicUrl (/app/server/node_modules/whatsapp-web.js/src/Client.js:1503:28)

Originally created by @robin-vandaele on GitHub (Oct 7, 2025). Original GitHub issue: https://github.com/guyzyl/whatsapp-contact-sync/issues/230 Description When running the app via the Docker variant, the sync process intermittently crashes with a Puppeteer error: Code Error: Execution context was destroyed, most likely because of a navigation. at rewriteError (/app/server/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:284:15) at async Client.getProfilePicUrl (/app/server/node_modules/whatsapp-web.js/src/Client.js:1503:28) This happens during the profile picture sync (getProfilePicUrl), causing the backend to stop responding. 🌍 Environment Deployment: Docker (combined backend + frontend image) Host OS: Linux (x86_64) ✅ Steps to Reproduce Build and run the Docker image as described in the README: bash docker build -t whasync . docker run --rm -it -p 80:80 whasync Open the web UI, scan the QR code with WhatsApp, and connect Google account. Start a sync with options manual_sync=false and overwrite_photos=true. After a few seconds, the backend crashes with the above error. 🤔 Expected Behavior The sync should complete successfully, updating Google Contacts with WhatsApp profile pictures. Puppeteer should remain stable during the entire sync process. ❌ Actual Behavior The backend throws Execution context was destroyed during getProfilePicUrl. Sync stops prematurely, and the container needs to be restarted. 📜 Relevant Logs Code /app/server/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:284 throw new Error('Execution context was destroyed, most likely because of a navigation.'); ^ Error: Execution context was destroyed, most likely because of a navigation. at rewriteError (/app/server/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:284:15) at async ExecutionContext._ExecutionContext_evaluate (...) at async Client.getProfilePicUrl (/app/server/node_modules/whatsapp-web.js/src/Client.js:1503:28)