Chrome headless screenshot on local machine - google-chrome

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.

Related

VS2017 Chrome Browser Debugger "Object reference not set to the instance of an object"

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.

Chrome debugger in Visual Studio Code gets stuck

If I try to start debugging in Visual Studio Code, I get the following error:
No matter what launch.json I use I always get this error. Tried a lot of launch.json configuration. Don't know why it tries to load localhost:9876/debug.html when I set the url to localhost:8100.
My app is running on 8100 port. Debugger for Chrome is plugin is installed. How could I get rid of this error?
The fix was quite easy. For a long time I did not make a restart to my computer. After a computer restart the debug is working now.

Chrome nativeMessaging example fails on Windows

I downloaded the official Chrome nativeMessaging example to test it out.
To do this, I installed the app from chrome://extensions, by choosing Load Unpacked. No problems so far.
I then installed the host. I'm using Windows 7, so I ran install_host.bat, which claimed that "The operation completed successfully." However, when I go to chrome://apps/ and click the Connect button, I get this error:
Failed to connect: Native host has exited.
Is there some reason this would happen? Restarting Chrome did not fix the issue, nor did uninstalling and then reinstalling the host program.
(I noticed that native-messaging-example-host.bat requires Python 2, so I modified it to run Python 2 explicitly. If I run native-messaging-example-host.bat from the command line, it pops up a little example program of its own with a GUI and seems to work correctly.)
Turns out I was using a non-standard character in the path leading to the host executable. This wouldn't be a problem for any other program, but Chrome's native messaging API doesn't like it, I guess.
By the way, the documentation on setting up this example is near-nonexistent, but this stack overflow link has some useful info: Chrome Extension NativeMessaging 'connectNative' undefined

While using Selenium and chromedriver in JMeter, I get an error on chrome

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.

Running without the SUID sandbox! while running source code for Chrome

I download chromium source code and compiled according to the instruction as stated on their website.
Now when I tried to run the binary file for chrom in out/Debug/chrom
I am getting this error
[17144:17144:0423/112117:FATAL:browser_main_loop.cc(169)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
my chrome folder is in the /home/user/chromium/src ..
Solved this!
when you run out/Debug/chrom and some error like this comes you can run $out/Debug/chrom --no-sandbox
at least the chrome will work then!