Opening google-chrome and starting any page will lead to "freezing". When start with terminal, it shows some errors:
ERROR: gpu_process_host.cc(956)] GPU process exited unexpectedly: exit_code=139
ERROR: gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
ERROR: command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
ERROR: chrome_browser_main_extra_parts_metrics.cc(228)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
ERROR: chrome_browser_main_extra_parts_metrics.cc(231)] crbug.com/1216328: Checking Bluetooth availability ended.
ERROR: chrome_browser_main_extra_parts_metrics.cc(234)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
ERROR: chrome_browser_main_extra_parts_metrics.cc(238)] crbug.com/1216328: Checking default browser status ended.
ERROR: platform_thread_posix.cc(147)] pthread_create: Resource temporarily unavailable (11)
I delete the repeated lines. Actually, this situation arise when I upgraded Ubuntu 18.04 to 20.04, and updated chrome to newest. I have no idea what's the problem about. I searched these output but seems nobody has similar problem.
By the way, vscode sometimes freeze like chrome after that upgrade. I don't know if there are any relationships...
What are you trying to do? Where these errors are getting displayed ? If you are using Selenium and you are getting these errors in the console then add these options into your Selenium code-
options = webdriver.ChromeOptions()
options.add_experimental_option('excludeSwitches', ['enable-logging'])
driver = webdriver.Chrome(options=options)
Related
First the Environment:
Node JS 16.15.0
Web Driver io v7 (wdio)
wdio/cucumber framework
end to end testing of a website
-obviously using cucumber and feature files
using a test configuration file similar to wdio's
using wdio-chromedriver-service v7.2.6 and npm chromedriver package version ^107 to produce a browser to hit
my browser : chrome v107.0.5304.62
The Question:
an element cannot be found by webDriver as I expect, but the command causes the instance to crash
I am searching for an element that no longer appears on the page (it is a spinner element that shows the page is loading)
I call
if(await this.spinner.isDisplayed())
and then the test run hangs, the debugger tells me the command
INFO webdriver: COMMAND findElement("css selector", "i.fa-spinner")
is running and then nothing else, finally the renderer times out
WARN chromedriver: [SEVERE]: Timed out receiving message from renderer: 600.000
DEBUG webdriver: request failed due to response error: timeout
and the chrome instance crashes shortly later
I am unsure why this behavior is happening, is something wrong with my wdio configuration? or with my chrome driver?
What I have tried
I understand that
browser.setTimeout exists but
I am sure it is not set in my config anywhere.
I have done a global search (using vscode for all development) for browser.setTimeout (no results).
I have manually set browser.setTimeout({ 'implicit': 0 }) (no success).
I have also tried directly hitting a chrome driver instance by manually downloading a chrome driver exe that matched my browser version v107.0.5304.62 and removing the 'services: ['chromedriver']'
from my test config file
when this happens something very interesting occurs, I can keep running after searching for the element that broke the run before, but we dont get very far and the command still causes issues. Chrome driver is throwing errors like
error: 'no such element',
[0-0] message: 'no such element: Unable to locate element: {"method":"css selector","selector":"i.fa-spinner"}\n' +
[0-0] ' (Session info: chrome=107.0.5304.87)'
The browser closes shortly afterwards without progressing through the rest of the tests.
I find it interesting that the version that chrome driver says it is running is 107.0.5304.87 since the version of chromedriver I downloaded clearly says it is v107.0.5304.62 and my chrome version clearly states it is also v107.0.5304.62 .
though theoretically using v107.0.5304.87 shouldnt be an issue according to this
since the 107.0.5304 part matches across the board
I could use some assistance.
We had the same issue this days, seems there is a bug introduced in Chrome 106; try to change config or downgrade Chrome on the machine to use Chrome 105 as with this version is working.
Since the upgrade my angular e2e tests started failing with following message.
I am using directConnect: true and all my tests are using async/await.
It looks it is crashing and does not always crash at the same point in my tests - and I do have some test running successfully. Disabled sharding as well.
- Failed: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=83.0.4103.61)
(Driver info: chromedriver=83.0.4103.39 (ccbf011cb2d2b19b506d844400483861342c20cd-refs/branch-heads/4103#{#416}),platform=Linux 3.10.0-1127.el7.x86_64 x86_64)
UPDATE: 6/1/2020
After adding more shared memory (finding CI runners that have more memory) this problem is gone. Still leaves the problem in a "mystery mode".
Update 6/2/2020:
Chrome Flags
'headless',
'verbose',
'w3c=false',
'disable-infobars',
'window-size=1440x1080',
'disable-dev-shm-usage',
'disable-gpu',
'incognito',
'disable-extensions',
'disable-plugins',
'no-sandbox'
I'm using chrome headless in podman and I've run into the same issue, here's what seems to work for me:
increase /dev/shm
remove "disable-dev-shm-usage" option
I needed the option in the past because it was impossible to change default /dev/shm size in a proprietary cloud software I'm using, looks like it's broken in the last chrome release.
The funny thing is - chrome also runs much faster after the changes
same here, after every update they want us to suffer, to find a pass to buddhism
I'm trying to enable in-app purchase inside my chrome extension. For that I've integrated with Google's buy.js lib.
Now when I attempt to purchase using this endpoint - google.payments.inapp.buy
I get the following error -
An unexpected error has occurred. Please try again later.
When I look at the console of the prompted paymet screen I see that there's a failed attempt to call a service at url -
https://224.32.32.55/29753 Failed to load resource:
net::ERR_ADDRESS_UNREACHABLE
It used to work in the past and stopped. What could be causing this?
I used to be able to use KWrite in the Fedora terminal fine, a few permission issues raised but weren't too problematic. However, I have been unable to open KWrite, although I can run scripts written in it fine. Whenever I try to open KWrite, I am given the message:
Qt: Session management error: None of the authentication protocols specified are supported "Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)"
This command does not seem to do anything helpful. Any ideas?
I keep getting the error while running functional tests using runner with following:
-selenium 2.44
-Chrome Driver
-Windows Server 2008 R2 Enterprise
Error Description: Listening on 0.0.0.0:7000
Starting tunnel...
UnknownError: [POST http://test.com/wd/hub/session / {"de
siredCapabilities":{"browserName":"chrome","name":"tests/intern","idle-timeout":
60,"selenium-version":"2.44.0"}}] unknown error: failed to write prefs file
(Driver info: chromedriver=2.12.301325 (962dea43ddd90e7e4224a03fa3c36a421281ab
b7),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any
stacktrace information)
Command duration or timeout: 1.06 seconds
Anyone have ever come across such issue? How do i fix this? Suggestions please
I've recently had the same issue. The problem was caused by full C drive. Apparently chromedriver needs some space in C drive (or the drive where chrome binary file is located) to create temporary profile files and so on.
One of the solutions could be to move chrome installation to some other drive. You could use mklink command in command line window.
It can be caused by executing ChromeDriver in parallel. Other errors as "failed to write first run file" or "cannot create default profile directory" may happen in that case.
My solution was to specify option user-data-dir. Two concurrent Chromedriver should not use same user data directory.
chromeOptions.AddArgument("--user-data-dir=C:\\tmp\\chromeprofiles\\profile" + someKindOfIdOrIndex);
You can of course change the path for whatever you want :)
This issue occurs if C drive disk runs out of space.The best solution to clear temp files.This solution worked for me.
Open Run command
2.Type % tmp%
3.Click on OK
4.Select all files.Delete all the files permanently.
you have different versions of chrome on server and on node
In my case, it was a consol application which should run as Administrator to gain access to the HDD
Follow These Steps
1)Press Window key+R
Type RUN
Type %temp%
4)Click Ok
5)Press Ctrl+A
Press Shift Delete