As advised by @John T. Haller i'm posting this here on the forums.
When using Google Chrome Portable - https://portableapps.com/apps/internet/google_chrome_portable - If you have any another instances of Chrome open (e.g Chromium, Chrome dev/beta, etc) the "Google Chrome Portable" process remains in the background. Only after all these are closed, the process in gone.
Is there something that can be done about this?
Also, about the lack of 64bit version on the Google Chrome package, is this the reason: https://portableapps.com/manuals/PortableApps.comLauncher/topics/64-bit....
?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Only a single instance of Chrome running at a time is currently supported. This is partially because Chrome is a very messy process that would require a lot of work to allow multiple Chrome-based apps to work concurrently and partially because the PA.c Launcher only currently supports running process name tracking rather than full path name tracking (aka we don't know which instance of chrome.exe is running).
As for 64-bit, there is a separate build of Chrome 64-bit available. It's labeled a test to keep it separate from the main stable 'channel' for the platform. It's the stable 64-bit version of Chrome. It will eventually be folded into the main package and it'll contain both 32-bit and 64-bit versions like Firefox does. This will take a good amount of work as Chrome Portable is kinda held together with duct tape at the moment and a lower priority as Chrome is only *barely* portable and you need to log into Google to use it to any degree due to all the settings purposely being locked per-PC by the publisher.
Sometimes, the impossible can become possible, if you're awesome!
Thank you very much for all the info, John T. Haller. And of course, for all the work you do here as well.
Regards