gildas-lormeau / single-file-cli

CLI tool for saving a faithful copy of a complete web page in a single HTML file (based on SingleFile)
GNU Affero General Public License v3.0
539 stars 57 forks source link

chrome.exe "zombie process" not terminated (Win 11, GoogleChromePortable) #96

Closed emp-00 closed 2 weeks ago

emp-00 commented 2 weeks ago

Boundary conditions:

Command line (reproducible example, happens with any website): single-file --browser-executable-path="D:\Single-File-cli_ChromePortable\GoogleChromePortable\GoogleChromePortable.exe" --browser-arg="--user-data-dir=D:\Single-File-cli_ChromePortable\GoogleChromePortable\Data\profile" "https://www.wikipedia.com" wikipedia.html

Symptoms:

Please try to reproduce, here it's 100% reproducible - also after system restart. Maybe it's caused by using Google Chrome Portable? Is the portable version not completely compatible with single-file-cli? I need to use a separate chrome(ium) browser with a separate profile for my project, that's why I chose Chrome Portable.

Currently I need to manually terminate the chrome.exe zombie processes (and the temporary files piling up) - would be great if this can be fixed. In case my command line is causing the issue, any help is appreciated! Thanks very much for the great tool, other than this, it's working perfectly!

emp-00 commented 2 weeks ago

I found the solution! It's required to use the downstream path to the actual "chrome.exe" of the Portable Chrome and NOT "GoogleChromePortable.exe" ! Maybe it's worthwhile adding this to the FAQ?

This works perfectly, it uses my profile as desired and no zombie processes and no temporary files remain - THANKS for the great tool, now my project can fly :-)

single-file --browser-executable-path="D:\Single-File-cli_ChromePortable\GoogleChromePortable\App\Chrome-bin\chrome.exe" --browser-arg="--user-data-dir=D:\Single-File-cli_ChromePortable\GoogleChromePortable\Data\profile" "https://www.wikipedia.com" wikipedia.html

gildas-lormeau commented 2 weeks ago

Thanks for the additional information. I'm glad to hear you found the cause of the problem.

In fact, there is no FAQ specific to SingleFile CLI yet. I'll move your bug report to the "Discussions" tab to make it visible to people.