Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leaves behind chrome processes #188

Open
nixtar opened this issue May 24, 2022 · 3 comments
Open

Leaves behind chrome processes #188

nixtar opened this issue May 24, 2022 · 3 comments
Assignees

Comments

@nixtar
Copy link

nixtar commented May 24, 2022

On windows with Chrome 101.0.4951.67 I'm seeing behaviour where every time I convert to HTML there is an additional ~4 chrome.exe processes that get started and not cleaned up.

After converting ~10 documents I ended up with this:
image

@nixtar
Copy link
Author

nixtar commented May 24, 2022

I should add, I had to manually download Chrome and use the ChromiumExecutablePath setting due to issues with our proxy server and the plugins built in downloading of Chrome. Possibly due to the version I downloaded?

Is there a URL to the version that the plugin tries to download for windows I can use to perform an "offline" install?

@manuth manuth self-assigned this Sep 16, 2022
@manuth
Copy link
Owner

manuth commented Sep 16, 2022

I'm not quite sure whether puppeteer allows me to get the URL it's downloading Chromium from but if so, I'll go try to include it into the UI somehow.

Thanks for letting me know and also thanks for using Markdown Converter ✨

manuth added a commit that referenced this issue Sep 26, 2022
This commit will fix part of #188
@nixtar
Copy link
Author

nixtar commented Sep 20, 2023

Update, managed to "convince" vs code to use our proxies and let the extension download Chromium natively.

This issue still occurs, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants