YusukeIwaki / puppeteer-ruby

A Ruby port of Puppeteer
Apache License 2.0
284 stars 41 forks source link

Web Socket didn't disconnect properly - stream closed in another thread (IOError) #319

Closed tanys123 closed 12 months ago

tanys123 commented 1 year ago
#<Thread:0x00007faffb5246a0 /Users/***/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/puppeteer-ruby-0.45.3/lib/puppeteer/web_socket.rb:67 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
        3: from /Users/***/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/puppeteer-ruby-0.45.3/lib/puppeteer/web_socket.rb:68:in `block in initialize'
        2: from /Users/***/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/puppeteer-ruby-0.45.3/lib/puppeteer/web_socket.rb:101:in `wait_for_data'
        1: from /Users/***/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/puppeteer-ruby-0.45.3/lib/puppeteer/web_socket.rb:44:in `readpartial'
/Users/***/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/puppeteer-ruby-0.45.3/lib/puppeteer/web_socket.rb:44:in `readpartial': stream closed in another thread (IOError)

Step To Reproduce / Observed behavior

It can be reproduced using the repo example.

Error happens when trying to disconnect the browser after accessing the page using evaluate, query_selector, etc.

Expected behavior

Browser should able to disconnect without any error

Environment

ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-darwin20]

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.