ggrossetie
commented
2 years ago After some time (and occasionally restarting the process)
Does it happen even if you don't restart (i.e., kill/restart) the process? In other words, do you think it leaves Chrome processes after a <CTRL> + <C>?
When watch or preview is enabled we do not close/restart the instance:
And we are using a single page (we only create a new page if there's no active page):
https://github.com/Mogztter/asciidoctor-web-pdf/blob/main/lib/browser.js
We could probably add logs in the browser.js to troubleshoot.
Also do you reproduce this issue when using Node.js directly (instead of the binary)?
I use the latest binary build of asciidoctor-web-pdf on Windows typically using the
--watchand often the--previewoptions. I think was the version:v1.0.0-alpha.12.After some time (and occasionally restarting the process) I often find I have many browser instances visible when I press Ctrl+Alt+Del and look at the processes, even though there is no open window. I usually notice this because the system is starting to slow down and I realise these browser instances are consuming excessive memory.
I'm not sure how best to diagnose this -- I'm sorry this is not a more helpful bug description. I hope to look into this more in future. The Windows system I most commonly use I don't have administrative rights to but perhaps I can pull out a process tree somehow.