pyppeteer / pyppeteer

Headless chrome/chromium automation library (unofficial port of puppeteer)
Other
3.61k stars 323 forks source link

websockets.exceptions.ConnectionClosedOK: sent 1000 (OK); then received 1000 (OK) asyncio.exceptions.InvalidStateError: invalid state #474

Open iamdaguduizhang opened 4 months ago

iamdaguduizhang commented 4 months ago

Python 3.8.19 pyppeteer 1.0.2 2.0.0

场景:访问google时,出现验证码,处理完验证码后,抛出异常

异常堆栈: connection unexpectedly closed Task exception was never retrieved future: <Task finished name='Task-960' coro=<Connection._async_send() done, defined at C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\pyppeteer\connection.py:69> exception=InvalidStateError('invalid state')> Traceback (most recent call last): File "C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\pyppeteer\connection.py", line 73, in _async_send await self.connection.send(msg) File "C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\websockets\legacy\protocol.py", line 635, in send await self.ensure_open() File "C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\websockets\legacy\protocol.py", line 944, in ensure_open raise self.connection_closed_exc() websockets.exceptions.ConnectionClosedOK: sent 1000 (OK); then received 1000 (OK)

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\pyppeteer\connection.py", line 79, in _async_send
        await self.dispose()
      File "C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\pyppeteer\connection.py", line 170, in dispose
        await self._on_close()
      File "C:\ProgramData\Anaconda3\envs\lazbao_work\lib\site-packages\pyppeteer\connection.py", line 151, in _on_close
        cb.set_exception(_rewriteError(
    asyncio.exceptions.InvalidStateError: invalid state
aarora4 commented 3 months ago

I am encountering this error as well.

gxl183718 commented 2 months ago

and me, please. my program has been working fine with native chrome. one day this error appears. but when i use other browsers, it works fine.