dgtlmoon
chrome cleanup error
Might this be related to all these stdout traps I'm getting? I get one every time a change detection is completed lol.
Same error here consistently (after during login using changedetection.io)
`2025-05-30 19:42:57.552 | INFO | main:stats_thread_func:627 - Connections: Active count 1 of max 10, Total processed: 2.
2025-05-30 19:42:57.556 | INFO | main:stats_thread_func:650 - Process info: 1 child processes
2025-05-30 19:43:00.094 | DEBUG | main:puppeteerToHere:615 - WebSocket ID: 6484aa77-17fe-4a3b-80e8-cdab7b45187d - Connection closed normally while receiving
2025-05-30 19:43:00.094 | DEBUG | main:stats_disconnect:215 - Websocket 6484aa77-17fe-4a3b-80e8-cdab7b45187d - Connection ended, processed in 37.268s
2025-05-30 19:43:00.095 | DEBUG | main:cleanup_chrome_by_pid:228 - WebSocket ID: 6484aa77-17fe-4a3b-80e8-cdab7b45187d Cleaning up Chrome subprocess PID 67
2025-05-30 19:43:00.098 | DEBUG | main:cleanup_chrome_by_pid:249 - WebSocket ID: 6484aa77-17fe-4a3b-80e8-cdab7b45187d - Killing 4 Chrome child processes
2025-05-30 19:43:00.100 | ERROR | main:cleanup_chrome_by_pid:308 - WebSocket ID: 6484aa77-17fe-4a3b-80e8-cdab7b45187d - Error in Chrome cleanup: Passing coroutines is forbidden, use tasks explicitly.
2025-05-30 19:43:00.100 | DEBUG | main:close_socket:199 - WebSocket: 6484aa77-17fe-4a3b-80e8-cdab7b45187d Closing websocket to puppeteer
2025-05-30 19:43:00.120 | DEBUG | main:hereToChromeCDP:576 - WebSocket ID: ad1e5abc-053c-4de8-9419-8724e3d93d9e - Connection closed normally while sending
2025-05-30 19:43:00.121 | SUCCESS | main:launchPuppeteerChromeProxy:543 - Websocket 6484aa77-17fe-4a3b-80e8-cdab7b45187d - Connection done!`
@VerbalP i guess you are the same person that emailed me, im lost, on your account with us it 100% works perfectly
@VerbalP i guess you are the same person that emailed me, im lost, on your account with us it 100% works perfectly
@dgtlmoon Yes, it's me. It works when the login fails (I had added dummy auth info before pausing the task). I've added back the proper credentials, it now fails: you can test/check logs
I have this as well. I'm using the sockpuppetbrowser together with changedetection. Interestingly enough it works perfectly fine during the browsers steps setup, but when triggering it via a check it fails
025-06-20 16:04:42.579 | DEBUG | __main__:hereToChromeCDP:640 - WebSocket ID: 786d60fb-2481-4d97-85bc-8132b544915b - Processing large message of size 51394 bytes
2025-06-20 16:04:42.601 | DEBUG | __main__:puppeteerToHere:692 - WebSocket ID: 06c33cfa-dc3b-40c8-8d38-2c3880eebf79 - Connection closed normally while receiving
2025-06-20 16:04:42.601 | DEBUG | __main__:stats_disconnect:284 - Websocket 06c33cfa-dc3b-40c8-8d38-2c3880eebf79 - Connection ended, processed in 7.761s
2025-06-20 16:04:42.601 | DEBUG | __main__:cleanup_chrome_by_pid:297 - WebSocket ID: 06c33cfa-dc3b-40c8-8d38-2c3880eebf79 Cleaning up Chrome subprocess PID 817
2025-06-20 16:04:42.602 | DEBUG | __main__:cleanup_chrome_by_pid:318 - WebSocket ID: 06c33cfa-dc3b-40c8-8d38-2c3880eebf79 - Killing 15 Chrome child processes
2025-06-20 16:04:42.603 | ERROR | __main__:cleanup_chrome_by_pid:377 - WebSocket ID: 06c33cfa-dc3b-40c8-8d38-2c3880eebf79 - Error in Chrome cleanup: Passing coroutines is forbidden, use tasks explicitly.
2025-06-20 16:04:42.606 | DEBUG | __main__:close_socket:268 - WebSocket: 06c33cfa-dc3b-40c8-8d38-2c3880eebf79 Closing websocket to puppeteer
/usr/lib/python3.11/asyncio/events.py:84: RuntimeWarning: coroutine 'wait_for' was never awaited
self._context.run(self._callback, *self._args)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2025-06-20 16:04:42.611 | DEBUG | __main__:hereToChromeCDP:640 - WebSocket ID: 786d60fb-2481-4d97-85bc-8132b544915b - Processing large message of size 50045 bytes
2025-06-20 16:04:42.611 | DEBUG | __main__:hereToChromeCDP:653 - WebSocket ID: 786d60fb-2481-4d97-85bc-8132b544915b - Connection closed normally while sending
This seems to return a 999 error to the webserver which causes it to break
