Bug on Browser Engine: `browser.newContext: Target page, context or browser has been closed.` about uptime-kuma HOT 5 CLOSED

• What exactly is returning this log message? the browser console or the node/docker log?
• To be able to reproduce this: what website are you monitoring? Is this reproducible?

from uptime-kuma.

I'm seeing this error in Kuma. The services are internal services (Jellyseerr, Radarr, Sonarr, Sabnzbd, and Scrypted)

This shot shows they all went down in the same check period.

Prior to that, they had all been up for about 6.5 hours when they all failed in the same way.

from uptime-kuma.

Thanks ^^
We might have a race condition in the playwright code as in https://stackoverflow.com/questions/61933492/playwright-error-target-closed-after-navigation

Given that this does not seem very widespread/reprducible I am not going to prioritse reproducing/debugging this (I am currently quite under the water Uni-wise).
If somebody else wants to give this a shot, here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

from uptime-kuma.

Added a simple fix in #4417 but I'm not sure if this is the root cause, you can help by testing it if you're interested.

https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests

from uptime-kuma.

@calebcall
I think this issue was fixed by #4417
Given that we cannot reproduce the issue, testing said PR would be greatly appreaciated ^^

I am going to assume that said PR works and does not contain bugs => closing as resolved

from uptime-kuma.