You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Errors generated by Restart Chrome Feature should be carefully handled
Current Behavior
By setting the new Restart Chrome Flag the performance is significantly improved on my machine (both CPU and memory as Chromium processes aren't endlessly spawned and kept around), however the script eventually fails as it does not handle the errors caused by restarting Chrome.
Am able to consistently reproduce this error but I do understand though if this is not a priority.
\streetmerchant\node_modules\puppeteer\lib\cjs\puppeteer\common\Connection.js:208
this._callbacks.set(id, { resolve, reject, error: new Error(), method });
^
Error: Protocol error (Network.setUserAgentOverride): Target closed.
at \streetmerchant\node_modules\puppeteer\lib\cjs\puppeteer\common\Connection.js:208:63
at new Promise (<anonymous>)
at CDPSession.send (\stock\streetmerchant\node_modules\puppeteer\lib\cjs\puppeteer\common\Connection.js:207:16)
at next (\streetmerchant\node_modules\puppeteer-extra-plugin-stealth\evasions\sourceurl\index.js:30:43)
at CDPSession.send (\streetmerchant\node_modules\puppeteer-extra-plugin-stealth\evasions\sourceurl\index.js:46:18)
at Plugin.onPageCreated (\streetmerchant\node_modules\puppeteer-extra-plugin-stealth\evasions\user-agent-override\index.js:180:18)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:94:5)
at async Plugin._onTargetCreated (\streetmerchant\node_modules\puppeteer-extra-plugin\dist\index.cjs.js:494:17)
npm ERR! code 1
npm ERR! path \streetmerchant
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c npm run compile && node build/src/index.js
npm ERR! A complete log of this run can be found in:
npm ERR! \npm-cache\_logs\2021-02-08T17_44_22_546Z-debug.log
Expected Behavior
Errors generated by Restart Chrome Feature should be carefully handled
Current Behavior
By setting the new Restart Chrome Flag the performance is significantly improved on my machine (both CPU and memory as Chromium processes aren't endlessly spawned and kept around), however the script eventually fails as it does not handle the errors caused by restarting Chrome.
Am able to consistently reproduce this error but I do understand though if this is not a priority.
Steps to Reproduce
Environment
Logs
The text was updated successfully, but these errors were encountered: