You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, I have made it wait 20secs at the end, enough to run check the mentioned defunct process.
I build the program with go build . and then I mount the binary in a docker container with the playwright runtime to test it:
$ docker run --name=bugdemo -ti -v $PWD/bugdemo:/mnt/bugdemo mcr.microsoft.com/playwright:focal bash
# /mnt/bugdemo
after dispose
after stop: <nil>
after cleanup. Waiting...
I open another shell in the container and check the running processes:
I have discovered that
playwright.Stop()
lefts behind a defunct process.It is possible to reproduce the problem doing this:
Create this simple Go program:
As you can see, I have made it wait 20secs at the end, enough to run check the mentioned defunct process.
I build the program with
go build .
and then I mount the binary in a docker container with the playwright runtime to test it:I open another shell in the container and check the running processes:
After 20secs, once the
bugdemo
process has finished, the defunct process disappears:I would expect
pw.Stop()
orpw.Dispose()
to cleanup the playwright runtime completly.The text was updated successfully, but these errors were encountered: