@mobrovac Do you know how we can solve this problem? In pure nodejs app we could listen to close or aborted events, but I have no idea how we can tackle that with our ServiceRunner. Can we access socket somehow via req variable here https://github.com/wikimedia/mediawiki-services-chromium-render/blob/master/routes/html2pdf-v1.js#L19 ?

So this sounds like the browser instance hasn't been terminated when expected. I haven't yet had time to really look into this, but it looks like there have been some changes [in the browser.close() API](https://github.com/GoogleChrome/puppeteer/commit/2b7951473d329d8e592750d68c61f689d651069b) which might help with this, so updating to [puppeteer v0.13.0](https://github.com/GoogleChrome/puppeteer/tree/v0.13.0) might help (and by looking at the list of changes since v0.11.0 would actually be advisable).

In general with fast-paced-developing software like puppeteer it's always a good idea to check if updates and/or issues might help with the problems that are being witnessed.

I'm not talking about puppeteer browser instance. I meant situation when user closes the tab.
An example situation: user clicks a link to render PDF, waits like 10-15 seconds and decides to close the tab and try again later. The job will stay in the queue, job will be picked up from the queue and rendering will start to happen even there is no open connection between user browser and the node service.

Oh right, right. In that case, the req object fires a close event which can be used in the service. So, something like:

req.on('close', () =>{
  // remove from queue
  // close browser window
});

in the route and/or logic should suffice.

(My comment about updating to the newest version of puppeteer still stands.)

Updating puppeteer has been moved to a separate task: T181097: Update puppeteer regularly.

Change 392932 had a related patch set uploaded (by Bmansurov; owner: Bmansurov):
[mediawiki/services/chromium-render@master] Abort render on connection close

https://gerrit.wikimedia.org/r/392932

Change 392932 merged by Pmiazga:
[mediawiki/services/chromium-render@master] Abort render on connection close

https://gerrit.wikimedia.org/r/392932

This is skipping QA. It was done as part of code review (Piotr used siege stress test tool)

Task is ready, tested locally, can be signed-off