[Bug]: Chrome not terminated on server

[maikelmotivo]

What happened?

When trying to view or store a PDF on the server we experience strange behaviour with the chrome processes. We have a hard time telling if it is an issue with this package, browsershot/puppeteer or maybe even a server sided issue.

How to reproduce the bug

When rendering a PDF using the code below we get a '504 Gateway Time-out' after 30 seconds, while locally it takes maybe 3 seconds to render. We noticed that the chrome process kept running, even for multiple minutes after the timeout.
Here comes the interesting part, when terminating the chrome process before the timeout, the browser proceeded to show the pdf immediately and correctly.

return Pdf::view('pdf.test')
    ->withBrowsershot(
        function (Browsershot $browsershot) {
            $browsershot
                ->addChromiumArguments([
                    'disable-gpu',
                    'disable-setuid-sandbox',
                    'no-sandbox',
                ]);
        }
    )
    ->name('test.pdf');

We also tested storing a PDF to a storage disk instead. Here we noticed the same behaviour. When trying to generate the PDF it would start chrome processes which proceeded to be active for several minutes. After a while chrome would be automatically terminated, and no PDF was written to the disk. However, if we manually kill the process at any time it would actually write the PDF to the disk immediately.

Is this a known issue, or is has this possibly something to do with server configuration?

Package Version

1.5.4

PHP Version

8.3.12

Laravel Version

11.35.1

Which operating systems does with happen with?

Linux

Notes

No response