EmptyReply on some watches after switching from Chrome to Playwright

[wrobelda]

Describe the bug
Switched to Playwright from Chrome engine and seeing an EmptyReply in one of the watches I had previously used without issues.
4 other watches I use with it seem to be fine, though. Additionally, one new watch I added today seems to be having the same issue.

Version
v0.39.15

To Reproduce

Steps to reproduce the behavior:

1. Add a watch for https://pcsupport.lenovo.com/pl/en/products/workstations/thinkstation-p-series-workstations/thinkstation-p340-tiny/downloads/ds544121-flash-bios-update-for-thinkcentre-m70q-m80q-m90q-thinkstation-p340-tiny?category=BIOS%2FUEF
2. Notice the "EmptyReply - try increasing 'Wait seconds before extracting text', Status Code None" error
3. Increasing said time doesn't help on my end.

Additional watch I have a problem with:

1. Literally any Aliexpress watch, e.g.: https://www.aliexpress.com/item/1005001496157027.html

Expected behavior
Playwright engine should capture a snapshot of a page without issues.

Desktop (please complete the following information):

• OS: macOS
• Browser: Safari
• Version: 15.5

[dgtlmoon]

1. I dont know what is "Chrome engine" - it's unsupported as far as I know :/
2. looks like it works from our paid subscription
   
3. try enabling this option, you may see more errors/information
   

[dgtlmoon]

let me know if it helps, especially step 3..

[walkamongus]

I'm ran into this issue after I updated images today and it turned out to be a browserless/chrome issue. I reverted back to the 1.52-chrome-stable version and issues went away.

[wrobelda]

let me know if it helps, especially step 3..

That didn't help. Still getting that issue frequently. I also logged in today, only to realize all of the Playwright-based checks were denoted as "[Errno 12] Cannot allocate memory".

I run docker stats and it looks OK to me:

CONTAINER ID   NAME                                    CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
ed2e76038a80   changedetection                         0.17%     1.293GiB / 3.856GiB   33.53%    2.3GB / 154MB     39.8MB / 484MB    15
bab172438d05   changedetectionio_playwright-chrome_1   0.58%     992.7MiB / 3.856GiB   25.14%    2.02GB / 2.43GB   683MB / 83.9MB    384

Restarting the changedetection container and manually triggering the checks fixed the memory issue, although the two checks I mentioned in my first post still finished with a EmptyReply - try increasing 'Wait seconds before extracting text', Status Code None

[marcosvrs]

The same happened to me when using the Playwright solution. Once I switched to WebDriver, it works smoothly.

[siccous]

I'm ran into this issue after I updated images today and it turned out to be a browserless/chrome issue. I reverted back to the 1.52-chrome-stable version and issues went away.

Helped me too.

[mariosemes]

Just to join in and add my two cents.
Had this issue on 50% of my watchers and found out that my selfhosted local instance of AdGuard was killing it for some reason.
After Disabling AdGuard DNS protection on my server and switching the DNS to something public like google or cloudflare, now it works flawlessly.

Hope this helps someone.