Disable Two Factor Authentification for this Google account and execute your Allow less secure apps. In these cases the respective solution would be to: Less secure apps can make it easier for hackers to get in to your account, so blocking sign-ins from these apps helps keep your account safe. In the article Less secure apps & your Google Account it is mentioned that, if an app or site doesn’t meet google-chrome's security standards, Google may block anyone who’s trying to sign in to your account from it. In majority of the cases the possible reason is, this particular user account is configured with Two Factor Authentification. In the article "This browser or app may not be secure" error when trying to sign in with Google on desktop apps Schaad mentioned that, if an user can log into the same app just fine with other Google accounts, then the problem must be with the particular account. This error can happen due to different factors as follows: implies that the WebDriver instance was unable to authenticate the Browsing Context i.e. : session not created exception from tab crashed error when executing from Jenkins CI server. You can find a couple of relevant discussions in: As per Comment61#Issue 736452 the fix seems to be have landed with Chrome v.6. Chrome crashes/fails to load when /dev/shm is too small, and location can't be overridden. Linux: Chrome/Chromium SIGBUS/Aw, Snap! on small /dev/shm. chrome_options.add_argument('-disable-dev-shm-usage')įrom tab crashed was WIP( Work In Progress) with the Chromium Team for quite some time now which relates to Linux attempting to always use /dev/shm for non-executable memory. This may slow down the execution though since disk will be used instead of memory. This will force Chrome to use the /tmp directory instead. It also works if you use -v /dev/shm:/dev/shm option to share host /dev/shmĪnother way to make it work would be to add the chrome_options as -disable-dev-shm-usage. So you may have to fix the small /dev/shm size.Īn example: sudo mount -t tmpfs -o rw,nosuid,nodev,noexec,relatime,size=512M tmpfs /dev/shm However as per UnknownError: session deleted because of page crash from tab crashed this issue can be solved by either of the following solutions:Īdd the following chrome_options: chrome_options.add_argument('-no-sandbox')Ĭhrome seem to crash in Docker containers on certain pages due to too small /dev/shm. 
There are diverse solution to this issue.
Why chrome driver not working for mac in selenium code#
Your code trials would have given us some clues what going wrong. The main exception is: : Message: unknown error: session deleted because of page crashįrom unknown error: cannot determine loading status
Though you see the error as: Error occurred while deleting cookies from web browser!ī'Message: invalid session idn (Driver info: chromedriver=51 (5d576e9a44fe4c5b6a07e568f1ebc753f1214634),platform=Linux 4.15.0-42-generic x86_64)n'
0 kommentar(er)
