Using existing userDataDir causes unknown failure with open tabs

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 1.13.0
• Platform / OS version: MacOS 10.13.6 and Chrome 74
• URLs (if applicable):
• Node.js version: 10.15.3

What steps will reproduce the problem?

I’m running this very basic code below and attempting to run puppeteer using my own chrome profile with userDataDir.

const puppeteer = require('puppeteer');
(async () => {
    try {
        const browser = await puppeteer.launch({
            executablePath: "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome",
            headless: false,
            userDataDir: '/Users/xxxx/Library/Application Support/Google/Chrome'
        });
        const page = await browser.newPage();
        page.on('console', msg => console.log('PAGE LOG:', msg.text()));
        await page.goto('https://google.com');
        await page.waitFor(10000);
        await browser.close();
    }
    catch (e)
    {
        console.log(e)
    }
})();

What is the expected result? Opening a new tab in my already open browser with my user profile.

What happens instead?

It fails silently (without any error message). An about:blank page does open as normal, but the other tab (google.com) does not.

$ node index.js
Error: Failed to launch chrome!


TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/Users/xxxx/.../node_modules/puppeteer/lib/Launcher.js:342:14)
    at ChildProcess.helper.addEventListener (/Users/xxxx/.../node_modules/puppeteer/lib/Launcher.js:332:60)
    at ChildProcess.emit (events.js:194:15)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)

Weirdly however, it does work somewhat when chrome is quit completely. It opens a new chrome with the correct, unsynced, profile. It also works when headless is set to true. It seems to be similar to issue 2099.

[aslushnikov]

Folks, please don’t run two browser instances that point to the same chromium profile. This will result in undefined behavior.

[maurijnvd]

Did you have any luck with this @TomasHubelbauer ? I have a similar issue - I have tried copying the chrome profile but got the same error as using Default, just wondering if you managed to get it working.

I had the same issue, it was fixed by the following 2 steps.

1. run service in Safari(or any other browser except chrome)
2. set the userDataDir to “/Users/YOURNAME/Library/Application\ Support/Google/Chrome/” beware the directory “default” was removed

Hi @zhiqinx what do you mean by ‘run service in safari’? What do i have to run in safari. I didn’t really get that.