existing chrome instances block launch

GoogleChromeLabs / carlo

Web rendering surface for Node applications

Apache License 2.0

9.32k stars 309 forks source link

existing chrome instances block launch #138

Open pkpkpk opened 5 years ago

pkpkpk commented 5 years ago

ubuntu 18.04, chrome 72

when using pkg . --target node10-linux-x64 and a chrome browser instance is already running:

Could not start the browser or the browser was already running with the given profile.

Without the browser already running, it works fine.
dev builds are fine independent of browser running or not
tried the fix suggested in #105, no luck
specifying --profile-directory & --user-data-dir in launch args key also fails

MckAudio commented 4 years ago

Had the same problem with multiple carlo instances on Win10.

The solution for me was to give each instance a unique localDataDir with carlo.launch({localDataDir: tmpPath}), for example a folder generated from an uuid in the temporary directory that could be removed afterwards.