Defunct process issue under latest version

[Using puppeteer-sharp under asp.net .net core 2.2 keeps defunct chrome processes when Puppeteer object is disposed]

Steps to reproduce:

1. Install asp.net core 2.2 api
2. With simple request call puppeteer, lunch browser, get content close browser
3. Observe a lot of defunct processes
4. Sooner or later observer Docker: “No space left on device”

 using (var browser = await Puppeteer.LaunchAsync(options).ConfigureAwait(false))
  {
                var allPages = await browser.PagesAsync().ConfigureAwait(false);
                var page = allPages.First();

                try
                {
                    await page.SetBypassCSPAsync(true);
                    await page.SetRequestInterceptionAsync(true).ConfigureAwait(false);

                    DisableMediaContent(page);

                   // navigation to page omitted here
                }
}

What I am doing wrong? Any recommendations are much appreciated. Thank you in advance.

[kblok]

I ran into some issues when running Puppeteer-Sharp on a machine with low resources. I did this:

_chromiumProcessID = browser.Process.Id;

public static void EnforceChromiumClose()
{
    var process = Process.GetProcessById(_chromiumProcessID);
    if (_chromiumProcessID > 0 && process?.HasExited == false)
    {
        process.Kill();
    }
}

Not clean at all. But if Chromium can’t gracefully close itself. I would force kill it.

[mesanja]

It’s turned out that issue is not related to puppeteer it self but for docker nature. In order to wipe zombies I used this solution https://github.com/Yelp/dumb-init. For anyone who faced with same issue, please use dumb-init.

Thanks all.