HamiguaLu
commented
1 year ago Hi, in my case, delete ProfileDir\Default\Preferences file fixed the issue I suggest after it works, backup the whole profile folder so later on you can recover
Open kSinghParth opened 2 years ago
HamiguaLu
commented
1 year ago Hi, in my case, delete ProfileDir\Default\Preferences file fixed the issue I suggest after it works, backup the whole profile folder so later on you can recover
alexliu0809
commented
1 year ago I was running multiple instances of UC. Besides using some of the fixes mentioned above, adding some wait time before launching each instance also helped.
Laishiji
commented
1 year ago I think it's some file broken in the profile dir, in my case, I compared the profile dir with another working one, then found there is a file named "Preferences" took 2.3GB, I deleted the file and Chrome can start now
Thank you. It works!!!!!👏
HerreraCarlos81
commented
1 year ago Could not find the ProfileDir folder. What am I missing here? 😑
freemedom
commented
1 year ago Could not find the ProfileDir folder. What am I missing here? 😑
--user-data-dir= must use this option can have custom ProfileDir. @HerreraCarlos81
Autolocsia
commented
12 months ago 2023 ends --user-data-dir= still not working
kenniky
commented
11 months ago Having the same issue with a test script I wrote:
import undetected_chromedriver as uc
options = uc.ChromeOptions()
user_agent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36'
options = uc.ChromeOptions()
options.add_argument('--headless')
options.add_argument('window-size=1400,1500')
options.add_argument('--disable-gpu')
options.add_argument('--no-sandbox')
options.add_argument('start-maximized')
options.add_argument('enable-automation')
options.add_argument('--disable-infobars')
options.add_argument('--disable-dev-shm-usage')
options.add_argument('--remote-debugging-port=9222')
options.add_argument('--user-data-dir=/home/ubuntu/chrome_profiles')
driver = uc.Chrome(options=options, version_main=110)
driver.get('https://nowsecure.nl')
driver.save_screenshot('screen.png')a bunch of the options are there because I've found they've been needed in the past on regular chrome
diroots
commented
10 months ago 2. The problem is with "SingletonLock" file, which you can find in the root of user profile folder. Just delete this file before starting Chrome and `Message: unknown error: cannot connect to chrome at 127.0.0.1:56401 from chrome not reachable` will never show again.
as of today with chrome 119 and latest 3.5.4 undetected_chromedriver, i got same problem when trying to launch chrome with options.add_argument('--user-data-dir=/path/to/my/profile') and i could see 3 Singleton*** files in the root of my profile : SingletonLock, SingletonSocket,SingletonCookie. these being symlinks, and even broken symlinks. removing them and restarting with my default options, i could reuse as expected.
hashtafak
commented
9 months ago I think it's some file broken in the profile dir, in my case, I compared the profile dir with another working one, then found there is a file named "Preferences" took 2.3GB, I deleted the file and Chrome can start now
Ha! Related to #1362 and some threads I've found on Stackoverflow. After running the same profile dir over time. Py.exe process eats the RAM from 2-5GB because of this file "Preferences".
anilabhadatta
commented
7 months ago @s-o-f great solution, this fixed my code... I was trying to create headless which was failing due to this but in non headless it was working. I was facing this issue in linux
anilabhadatta
commented
7 months ago https://github.com/anilabhadatta/educative.io_scraper/blob/v3-master/src/Utility/BrowserUtility.py the implementation that I used to spawn Chrome/ Chromedriver and close it is working for me To close the process: asyncio.get_event_loop().run_until_complete(browserUtil.shutdownChromeViaWebsocket())
iohansson
commented
7 months ago for those who are running headful Chrome on a server, check that you have Xvfb running.
I had the same issue trying to run my script with Docker, looked into the undetected_chromedriver docker image entrypoint and found the following among the lines
#!/bin/bash
function keepUpScreen()
{
echo "running keepUpScreen()"
while true; do
sleep 1
if [ -z "$(pidof -x Xvfb)" ]; then
Xvfb $DISPLAY -screen $DISPLAY 1920x1080x16 &
fi
done
}
export DISPLAY=:1
rm -f /tmp/.X1-lock &>/dev/null
keepUpScreen &
echo "running: $@"
exec $@So I've created an entrypoint with this, and that solved my issue.
johnwhelchel
commented
6 months ago This is not documented anywhere, but I've recently found that if you don't call driver.quit(), the temp directory used for a user directory is not cleaned up. It's quite confusing, because using the driver as a context manager should implicitly clean up resources, but it doesn't (based on implementation of exit https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/1614).
This seems to have fixed the issue for me.
victorbjafet
commented
3 months ago Found a solution for the problem. forget about all the extra arguments and updates/ etc.
If you are using the DIR folder that currently has a browser profile open. it will not work. you have to close everything first and then run it. That was the workaround for it for me.
@kSinghParth @wundergeu @Habidis
thank you so much, this worked for me. make sure that you check your task manager/windows tray to see if chrome is running in the background, which was my case
Hey,
I am running a script on a headless server via ssh. The script was working fine until about a week ago. I made some minor unrelated changes, post which undetected-chromedriver started failing. I am attaching a very simplified code below.
I get the following stdout/stderr
The complete stack trace is
Driver verbose logs.
Operating System: Ubuntu 16.04.7 LTS Kernel: Linux 4.4.0-210-generic Architecture: x86-64
$ chrome --version Google Chrome 103.0.5060.134 unknown $ which chrome /opt/google/chrome/chrome $ python --version Python 3.7.7
undetected-chromedriver==3.1.5.post4
If I simply try to run selenium headless, I am facing no problems. Any help would be appreciated. Thanks.