Haven't used browsertrix for some time, so moved from 1.7.1 to 1.12.4
Using browsertrix on Linux commandline
same issue with 1.10.3 but 1.9.0 and 1.7.1 are ok
same issue with or without --profile
same issue using the basic "getting started" commands from the docs
error v1.12.4
"Unexpected error, interrupting","details":{"type":"exception","message":"The browser is already running for /crawls/collections/2604test_20/profile. Use a different userDataDir or stop the running browser first.","stack":"Error: The browser is already running for /crawls/collections/2604test_20/profile. Use a different userDataDir or stop the running browser first.\n at ChromeLauncher.launch (file:///app/node_modules/puppeteer-core/lib/esm/puppeteer/node/BrowserLauncher.js:139:23)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Browser._init (file:///app/dist/util/browser.js:343:24)\n at async Browser.launch (file:///app/dist/util/browser.js:83:9)\n at async Crawler.crawl (file:///app/dist/crawler.js:1210:9)\n at async Crawler.run (file:///app/dist/crawler.js:393:13)\n at async file:///app/dist/main.js:63:1"}}
error v1.10.3
"message":"Crawl failed","details":{"type":"exception","message":"The browser is already running for /crawls/collections/2604test_10/profile. Use a different userDataDir or stop the running browser first.","stack":"Error: The browser is already running for /crawls/collections/2604test_10/profile. Use a different userDataDir or stop the running browser first.\n at ChromeLauncher.launch (file:///app/node_modules/puppeteer-core/lib/esm/puppeteer/node/BrowserLauncher.js:138:23)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Browser._init (file:///app/dist/util/browser.js:393:24)\n at async Browser.launch (file:///app/dist/util/browser.js:81:9)\n at async Crawler.crawl (file:///app/dist/crawler.js:1149:9)\n at async Crawler.run (file:///app/dist/crawler.js:394:13)\n at async file:///app/dist/main.js:58:1"}}
Haven't used browsertrix for some time, so moved from 1.7.1 to 1.12.4
Using browsertrix on Linux commandline
same issue with 1.10.3 but 1.9.0 and 1.7.1 are ok
same issue with or without --profile
same issue using the basic "getting started" commands from the docs
error v1.12.4
"Unexpected error, interrupting","details":{"type":"exception","message":"The browser is already running for /crawls/collections/2604test_20/profile. Use a different
userDataDiror stop the running browser first.","stack":"Error: The browser is already running for /crawls/collections/2604test_20/profile. Use a differentuserDataDiror stop the running browser first.\n at ChromeLauncher.launch (file:///app/node_modules/puppeteer-core/lib/esm/puppeteer/node/BrowserLauncher.js:139:23)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Browser._init (file:///app/dist/util/browser.js:343:24)\n at async Browser.launch (file:///app/dist/util/browser.js:83:9)\n at async Crawler.crawl (file:///app/dist/crawler.js:1210:9)\n at async Crawler.run (file:///app/dist/crawler.js:393:13)\n at async file:///app/dist/main.js:63:1"}}error v1.10.3
"message":"Crawl failed","details":{"type":"exception","message":"The browser is already running for /crawls/collections/2604test_10/profile. Use a different
userDataDiror stop the running browser first.","stack":"Error: The browser is already running for /crawls/collections/2604test_10/profile. Use a differentuserDataDiror stop the running browser first.\n at ChromeLauncher.launch (file:///app/node_modules/puppeteer-core/lib/esm/puppeteer/node/BrowserLauncher.js:138:23)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Browser._init (file:///app/dist/util/browser.js:393:24)\n at async Browser.launch (file:///app/dist/util/browser.js:81:9)\n at async Crawler.crawl (file:///app/dist/crawler.js:1149:9)\n at async Crawler.run (file:///app/dist/crawler.js:394:13)\n at async file:///app/dist/main.js:58:1"}}