In the console, I get 9 issues where 8 of them are marked in red but with no messages about 8 red issues. like in the following screen, what red marked issues mean?! chrome dev tool
Here I have 92 red marked issues
Related
When I want to inspect a page listed on chrome://inspect page on a remote Pixel 4 with OS version 11, I get a white page with just 'HTTP/1.1 404 Not Found' shown.
I uninstalled all updates from Android Chrome, went down to version 83, and remote debugging started working again.
I have the same problem with current versions of Chrome beta/dev/canary.
Is this only a problem on my device, or a general problem? Any way to get remote debugging working with Chrome 89?
Thanks,
Michael
It seems you can't get it working on Chrome 89 for now because this is a general problem. I got the same issue on Vivaldi 3.7 which runs Chromium 89. The only option for now is rolling back to previous working release.
I'm currently working to maintain an existing PNaCl application for ChromeOS devices. Prior to Chrome 72, we were able to log to stdout and stderr and these logs would appear on the ChromeOS device inside the ui.LATEST file. Since our ChromeOS devices have upgraded to versions past Chrome 71 our logs do not appear any more. We've tried this on devices running both Intel and ARM chipsets with the same results. We are using Pepper 49 (the latest). Our development environments in Ubuntu are still outputting to the stdout and stderr.
Has there been a change in Chrome 72 to where stdout and stderr log to or how we log to the ui.LATEST file?
EDIT: We've tried a couple of other sites that we know log to the stdout and use PNaCl, namely this: https://gonativeclient.appspot.com/demo - this also does not log to the Chromebooks but does log in our development environments.
We have a .NET program to run headless Chrome to snapshot web page to image, and here is the sample code:
class Program
{
static void Main(string[] args)
{
var p = Process.Start(
#"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe",
$#"--headless --screenshot=E:\test{DateTime.Now:HHmmss}.png --disable-gpu --window-size=320,568 http://www.microsoft.com");
p.WaitForExit();
}
}
The console application is scheduled in Windows Task Scheduler with "Run whether user is logged on or not" option. The program works fine for months but failed yesterday, we noticed the Chrome version is 73 now. Luckily we found a computer in which Chrome is still 72, so we tested the background scheduled task once, upgraded Chrome to 73 and tested it again, finally got the conclusion - Headless Chrome 72 can run in background, but Chrome 73 can't.
Does anybody find the same issue on Chrome 73?
[updated on 2019/6/23]
It's a bug of Chromium (bug 942023) and has been fixed on Chrome 74.0.3729.108.
For Chrome 73, you can use --disable-features=VizDisplayCompositor argument as a workaround.
Yes, we have the same issue here. We're running Chrome through Selenium WebDriver and after the update to Chrome 73 our background tasks no longer function correctly. Downgrading to Chrome 72 fixes the problem.
Our diagnostics logs show that when running Chrome 73 in headless mode that certain calls to the Chrome process seem to hang. For instance, resizing the browser or trying to take a screenshot via the WebDriver API. We tried a number of things to fix this including updating Selenium, WebDriver and chromedriver to the latest versions but all had identical behaviours.
There certainly seems to be an issue with running Chrome 73 in headless mode after the update.
I'm using chrome on Windows 7 and after updating from 48 to 49, the devtools get frozen when I'm trying to navigate some of the tabs (sources, resources, etc.)
I re-installed several times, and restored devtools options to default, but none of the attempts worked for me.
I downgraded to 43 and works fine.
Anyone knows the reason or experiencing same problem?
I was debugging blackberry apps from Eclipse. It works fine at the beginning but since some days ago, I could no longer get the app onto any emulator or device.
The packaging and signing shows NO error. After it displays the "debugger attaching..." screen, I could not find the app anywhere on the emulator or device. I have tried to reinstall the eclipse and JDEs a few times. One observation is that it had about 280 files to sign. Without any changes in the code now it has 540 files to sign.