Romain Dorgueil

Update: Still strugling in tracing that but it looks like it happens because `page.close()` is awaited too soon after the `page.goto(...)` went timeout. I reduce greatly the amount of errors...

@miyakogi Thanks for the reply. I can confirm for sure that it is not docker related, I just spent some time installing my code on a machine without containers, and...

Related websocket log : ``` DEBG:0087:websockets.protocol: client > Frame(fin=True, opcode=8, data=b'\x03\xe8', rsv1=False, rsv2=False, rsv3=False) DEBG:0087:websockets.protocol: client - eof_received() DEBG:0087:websockets.protocol: client ! failing WebSocket connection: 1006 DEBG:0087:websockets.protocol: client - connection_lost(None) DEBG:0087:websockets.protocol:...

@miyakogi Unlike everything I believed until then, it seems the error happens because of something the remote site has. Can't understand why, but I can reproduce it 100% (whatever the...

Note that the equivalent puppeteer code on the same website works as expected and does not close the websocket connection: ```javascript const puppeteer = require('puppeteer'); (async () => { const...

Here are some other examples of urls that produce this bug: ``` https://www.iu.edu/ http://www.teletape.info/ ``` One challenge is that not all urls reproduce the bug on all origins. I suspect...

@miyakogi That's quite unexpected, should be completely unrelated, but on my local box it looks like the it works for the urls I listed here. Unfortunately, I upgraded a few...

Oh and thanks for looking into it, I understand it may take some time as I already spent around 1 full week struggling with this, really hard to trace (but...

So, update here. Indeed it looks like the patches "mostly" fixes the problem. I still have it on some websites (but not 100% reproductible, looks like the behavior is a...

As far as I know, it is not fixed. I still have the problem from time to time even if using develop makes it happen way less often. @miyakogi any...