I have a problem with chromium when I run my tests through the puppeteer.
What happens is that my tests require the microphone to be enabled the moment I log in to the application, even after adding:
'--use-fake-ui-for-media-stream', '--no-sandbox', '--disable-setuid-sandbox'] : ['--use-fake-ui-for-media-stream'
Before working normally, after changing the machine it stopped working and I don't know if it is related to the version of the chromium that is started:
This is the version of chromium when testing starts:
Version 77.0.3844.0
And my version of the puppeteer is:
```"puppeteer": "^1.19.0"````
Has anyone ever experienced this? If so, how do I update the chromium?
Thanks,
Related
I am having trouble debugging my web project using the Chrome Browser. I can only use IE to do my debugging. I did some "googling" to resolve this problem, and came across a few Microsoft threads that said to update to the latest version of VS2017, which I did. I use version 15.9.13 and Visual Studio 2017 tells me I am "up to date" when I check for further updates.
When I first updated VS 2017, it started working, and I could debug using Chrome (finally!). But now it has stopped working again.
I saw in other threads where people suggested deleting the .vs folder, which I did, but had no luck with that.
Google Chrome is up to date at Version 75.0.3770.100
I debug and run my application as "Administrator" so that shouldn't be the problem either. I also close all browsers before running the debugger, so Chrome isn't running elsewhere when I try to debug.
Is there any explanation why Chrome cannot launch when using debugger? I would really like to use Chrome because of it's superior "dev tools" and inspection tools. Any suggestions? Was sad to have it working only one day.
Having configured the same environment like yours(VS version and Chrome version) but can't reproduce the issue.I would think if something is broken in VS or maybe third-party extension is the causes this issue.
Please try:
VS repair and a reinstall of Chrome(don't forget to backup the bookmarks)
Uninstall or disable third-party vs extensions, this won't take effect until restart vs
Navigate to %LocalAppData%\Microsoft\VisualStudio\15.xxx directory, delete all ComponentModelCache folders in all 15.xxx folders.
Open your project in vs, changed the target browser from Chrome to IE. Then F5 and wait until it is finish. Stop it and change the browser back to Chrome. After that the error disappeared.
Also, create a new asp.net web app and debug it with Chrome browser to check if the issue persists. Hope it helps.
I have a localhost website created with ember which is just working fine.
I want to use Lighthouse to get some metrics about the performance over time. Of course I want this to be in Chrome and headless. I installed Lighthouse using NPM and run the following command:
lighthouse http://localhost:4200 -chrome-flags='--headless'
When running above, I got the following error resulting in a question mark as a performance metric:
Chrome didn't collect any screenshots during the page load. Please make sure there is content visible on the page, and then try re-running Lighthouse. (SPEEDINDEX_OF_ZERO)
I tried running the dist folder of ember with the http-server package, but no differences in the result. The same error occurs.
When I run the test against google.com or against a website in our test environment I get a result back and not the error. When a colleague is running it on his local machine, no error occurs. Only difference we can find is he is running win8.1 and my machine is win10.
When I run Chrome without the headless flagg I also get a result, but I need it to work headless.
I'm using all the latest versions of Lighthouse, Chrome, Windows10, node. Also tried Chromium but no differences.
Hopefully someone got an idea
After a week I tried again, still the same error. Now I tried again and it works. Nothing changed to my codebase and all apps, packs and so on are also the same version which I can see.
I don't know what fixed the issue, but it works now. Case closed.
I'd like to set up Chrome in headless mode and the ChromeDriver for Selenium testing on my PythonAnywhere instance. I can't find any instructions on how to sort this out. Does anyone have any advice/pointers to docs please?
Meanwhile it works: you simply have to write an email to the PythonAnywhere support and they will enable it for your account (here are some details).
PythonAnywhere dev here -- unfortunately Chrome (headless or otherwise) doesn't work in our virtualization environment right now, so it won't work :-(
[edit] ...but now it does! See #Ralf Zosel's answer for more details.
I have inherited a JMeter performance testing script. There is a chromedriver section and an HTTPSampler section. The httpsampler section works fine. The chromedriver section runs into a problem. When I run it chrome pops up like this:
It does not move forward with any of the steps in the plan after that. Up until recently I've also been seeing the error
Error communicating with the remote browser. It may have died.
I am not seeing this now, so I don't know if it's just a difference in how the test is running or what.
The person I inherited this from was running it on a mac and did not get any of these problems. I saw it run with no errors at the same time I was getting them.
One solution I found was to add the --test-type flag to chromedriver. Unfortunately I cannot find a way to add that argument when running it through JMeter. I've tried adding both --test-type and -test-type to the end of the path to chromedriver.exe, but that did not work.
Does anyone have a solution for this?
The error might be due to conflict in chrome driver version. Please install the latest version of ChromeDriver from this link.
Latest version of Chrome Driver supports the browser version v56-58.
I am using Ubuntu 12.10. When I try to install themes, extensions for Google Chrome browser from Chrome Web Store it shows the following error:
Could not install package:
'UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL'.
Could not install package because a utility process crashed.
Try restarting Chrome and trying again.
I don't know what to do. And I can't find a proper solution.
This is an unidentified bug in Chrome that made a lot of noise.
Since Chrome developers could not obtain feedback about this bug in time, they marked it as WontFix. So simply waiting for a new version will most probably not help.
Closing for lack of actionable input on the bug.
If someone runs into this, please open a new bug!
You (yes, you, 007!) can actually help everyone running into this bug. Create an issue at crbug.com, mentioning the old issue #401655 and following the debug steps outlined in that issue report, esp. this comment.
That said, the bug is correlated with the kernel version used. Ubuntu 12.10 is no longer supported since 2014-05-16. You probably should move to 14.04 LTS release where this bug is not present.
But if you can't do that for whatever reason, and/or are willing to help Chrome development team, please investigate and make a bug report! And add a comment afterwards pointing to the bug you make.
Thank you for helping us help you help us all.
-- GLaDOS, Portal
version 46.0.2490.80
Fixed utility_process_crashed_while_trying_to_install issue as below:
modify the crx suffix to zip, e.g foo.crx->foo.zip
unzip the foo.zip to one folder, c:\chrome\foo
open chrome://extensions/
enable Developer Mode
"load unzipped extensions" and open c:\chrome\foo
foo.crx loaded successfully.
As crx is zip file and only htm, json, js files included, it's chrome bug and
hope this workaround will help you to avoid uninstall/install/upgrade pain :)
It is a bug in chrome, please downgrade your chrome browser or please wait for new version.