Why does this "Slow network detected..." log appear in Chrome? - google-chrome
I noticed this info log began to appear in Google Chrome Dev (Version 55.0.2883.18 dev) and I can't imagine why.
Slow network is detected. Fallback font will be used while loading: http://font-path.extension`
It appears on all websites that use font-face, even on local pages and Chrome extensions.
This means the network is slow, and Chrome is replacing a web font (loaded with a #font-face rule) with a local fallback.
By default, the text rendered with a web font is invisible until the font is downloaded (“flash of invisible text”). With this change, the user on a slow network could start reading right when the content is loaded instead of looking into the empty page for several seconds.
Related Chrome issue: https://bugs.chromium.org/p/chromium/issues/detail?id=578029. (A change enabling this behavior for 3G connections landed in September; this should be the reason you got the message.)
Related source code: https://chromium.googlesource.com/chromium/src/third_party/+/master/WebKit/Source/core/css/RemoteFontFaceSource.cpp#74
I faced same issue for chrome build 61.0.3163.100 on MacOs Sierra with localhost as server. Chrome started logging this message when I changed network speed configuration to 3G fast/ 3G slow and again back to Online.
Fix:
When I tried selecting Offline mode and again Online mode, the logging issue disappeared. (This fix may no work on some devices or versions)
Update on 30th Jan 2018
I updated google chrome to Version 64.0.3282.119 (Official Build) (64-bit), it seems this bug is fixed now.
EDIT: This is not working with latest version of 63.0+
I was able to disable it using help from one of above comments, go to
chrome://flags/#enable-webfonts-intervention-v2
The trick is to also disable the "Trigger User Agent Intervention for WebFonts loading always" option just below that as well.
In my case, it was AdBlock Plus extension for Google chrome. Turned it off and it worked perfectly.
if you can access to css of this extension, simply add font-display:block; on font-face definition or send feedback to developer of this extension:)
#font-face {
font-family: ExampleFont;
src: url(/path/to/fonts/examplefont.woff) format('woff'),
url(/path/to/fonts/examplefont.eot) format('eot');
font-weight: 400;
font-style: normal;
font-display: block;
}
I hide this by set console setting
Console settings -> User messages only
Goto chrome://flags/#enable-webfonts-intervention-v2 and set it to disabled
It’s due to a bug in Chrome with their latest API for ‘network speed’. Hope it will be fixed in the next version
I have network throttling disabled but started to get this error today on a 75mb/s business connection...
To fix it in my build of Chrome 60.0.3112.90 (Official Build) (64-bit) I opened the DevTools then navigated to the DevTools Settings then ticked 'Log XMLHttpRequests', unticked 'User messages only' and 'Hide network messages'
I just managed to make the filter regex work: /^((?!Fallback\sfont).)*$/.
Add it to the filter field just above the console and it'll hide all messages containing Fallback font.
You can make it more specific if you want.
If your developing an app that uses google fonts and want to ensure your users do not see these warnings. A possible solution (detailed here) was to load the fonts locally.
I used this solution for an application which at times has slow internet (or no internet access) but still serves pages, This assumes your app uses Google fonts and updates to these fonts are not critical. Also assume that using ttf fonts are appropriate for your application WC3 TTF Font Browser Support.
Here is how I accomplished locally serving fonts:
Go to https://fonts.google.com/ and do a search for your fonts
Add your fonts
Download them
Place them in site root
Add them to your #font file
No, this doesn't mean network is slow.
No, this is not only false warning.
I have this problem on angular web applications after replace link https://fonts.googleapis.com/icon?family=Material+Icons in index.html to integrated version (npm install .... material-icons...). This works, but sometimes web application show that warning.
When warning is shown icons are not rendered for approximately 1 second, so user see badly rendered icons.
I don't have solution yet.
I also had the same errors with fontawesome's fonts.
Then I downloaded the lastest fontawesome's fonts and replace to the old fonts.
And the errors are gone.
The easiest way to disable this is uncheck the warnings in the chrome dev tools
Hope this helps.
you can click 'console settings', and check then box 'Use messages only', after that those messages won't show again.
Updating to the latest version of Chrome (63.0.3239.84) via Help -> About fixed it for me.
(actually, I did had to switch to Offline and back to Online in the Network tab of developers tools to make the last errors go away.)
As soon as I disabled the DuckDuckGo Privacy Essentials plugin it disappeared. Bit annoying as the fonts I was serving was from localhost so shouldn't be anything to do with a slow network connection.
Right mouse сlick on Chrome Dev. Then select filter. And select source of messages.
I've noticed if I use the 'woff' version of the font alone, I got this latency warning message. But if I add the 'ttf' version, the warning disapear. As I'am using a local web application, I made a tradeoff as of the size of font file.
font-face {
font-family: Rakaba;
src: url(../assets/font/web/Rakaba-Bold.woff) format('woff'),
url(../assets/font/Rakaba-Bold.ttf) format('ttf');
}
Related
What does bis_skin_checked="1" mean? It's showing on most of my elements when using chromes code source view?
I'm confused I don't know if the latest update of chrome AKA version 73 just integrated this attribute on purpose but I'm getting a strange attribute that I did not added into my web pages and i'm wondering what this means in chrome? CHROME BROWSER EDGE BROWSER Should I be concern with this? It's only showing on Chrome.
There is another Chrome and Firefox plugin that does same, sadly, but probably one of best VPN tools Urban VPN Browser Extension. The solution is same, just deactivate. Btw, those guys have other extensions, haven't tested others.
Just uninstall any type of VPN that you installed in you browser and afterwards bis_skin_checked="1" will removed automatically.
The attribute is added just because of one of an extension of the Chrome Browser you have installed in your Chrome Browser. I also got this attribute added to my HTML when checking in the console. Then I replicate this by deactivating extensions one by one and found it's adding from Hover Over extension.
This problem has happened to me recently. I installed the Urban VPN plugin and after that, I faced this issue. But uninstalling the plugin, the problem is solved.
I've got the SpeakIt! [Version 0.3.20] extension installed for Chrome [Version 74.0.3729.131 (Official Build) (64-bit)] on Windows 10, and I am seeing the same bis_skin_checked="1" when it's enabled. When I disable the SpeakIt! extension, the bis_skin_checked="1" goes away.
This thing append from different Chrome/Mozilla extension. Disable recent extensions to see the changes(bis_skin_checked="1" goes away ).
Google Chrome developer tools works very slow
Sinсe Google Chrome was updated to 50.x version, it become impossible to work with DevTools. This issue reproduced mostly in "Network" tab. Every time when you click on "request" it takes about 30-40 sec. after that chrome can crash. Tried to delete all extensions, clear cache, and reinstall, but didn't help. Does anybody know how to fix this issue? I'm running Chrome 50.0.2661.87 m UPD: The problem may be occurs because of long headers. Try to close response and request headers.
I've been having similar issues for debugging in Chrome versions 50+ on Mac OS X 10.11.3. The only solution I've found so far is to keep the dev tools docked to the right and it seems to be as performant as before. Not the optimal solution, but it works in my case.
Finally, a solution has been found which helped me after such a long time and after so many failed attempts to fix it: Solution on Google Chrome Forums Go to chrome://flags/#force-color-profile Change it to sRGB Since Google does not allow direct links to chrome:// you'll have to insert the colon by yourself, or enter the whole link manually into your toolbar.
My situation was similar, after struggling a while with extreme slow developer tools response I found out the problem was caused by a Chrome extension I had installed for knockoutJs. So for people experiencing these issues, as part of the initial troubleshooting, try disabling chrome extensions.
I'm using the Version 61.0.3163.79 and I have the same issue that this post talks about. With some searches I found out that the problem was in the user that I was using. What I tried was to enter int google chrome as guest and the devtools became faster again. So what I did was: Check out if debugging using the guest user is faster as it should be. Logout from the account. Clean all cache associated to google chrome. Restart the PC (but i think closing the browser is enough) Login again in your account. I hope this could help other people with same problem. [EDIT:] I found out that after some time (weeks) the google chrome dev tools will get slower again. So I tried the following solution and it worked: Open the dev tools Go to the Sources tab. Cleaned all watched variables, breakpoints, DOM breakpoint and Event Listeners breakpoint. [SECOND EDIT:] After some weeks, the issue came again. What I did was installing the google canary Version 64.0.3249.2 canary (64-bit) and my problems vanished. For who's that doesn't know what is canary, please check this link.
Google is aware of the problem - https://bugs.chromium.org/p/chromium/issues/detail?id=624097 The problem seems to have vanished in v.53 - they are currently trying to figure out what fixed it. If possible, the fix will be merged back to v.52. But at least they are working on it.
In case others arrive here facing the same issue I had, try changing the Dev tools tab you're looking at to Elements. I had the "Sources" tab open and Chrome was trying to load enormous assets for that tab, which created a multisecond delay between the console.log() events I created and the display of those logged messages.
Make devtools snappy again by deactivating all breakpoints: Go to the Sources tab, show the debugger (may be hidden) and hit Deactivate breakpoints. (Chrome v62.0 on Windows 10)
I've had the same time issue on 54.0.2840.99 m version of Google Chrome. But switching to Chrome Canary worked !
Reduce size of resource being overridden Only overriding files with less lines of code worked well for me. I landed here because I was overriding a file which had 35,000 + lines of Javascript. Further, if your resource is a new one - i.e. it is not included in a script tag or link tag, you can override main html document and add the tag : <script src="/my-new-script.js"></script>. Add the file to your domain-root within the Overrides folder on Chrome: overriding HTML then overriding CUSTOM SCRIPT: Good Luck...
I also face same issue. I tried unchecked toggle screencast. Now it is working fine.
In my case, I had Local Overrides setup (https://developers.google.com/web/updates/2018/01/devtools#overrides) in Downloads folder which had a lot of files in it and that slowed down devtools. Setting up overrides in its own seprate directory fixed the slowness.
I sped up Chrome again by doing the following: Open DevTools -> select Elements tab -> select nested Computed tab -> under Filter, make sure that Show all is unselected. select nested Event Listeners tab -> make sure that Ancestors and Framework listeners are unselected.
For me, running Chrome Version 81.0.4044.138 (Official Build) (64-bit) on Ubuntu 18, the problem seems to be the mobile view. When I disable mobile view inspecting becomes really fast again. I think it is caused by touch emulation and other mobile stuff. To have something similar to a mobile view I move the DevTools dock to the side and resize it until I get the width I need. It is not perfect, but it is useful most of the time. Besides Chrome, Firefox is much faster when inspecting sites overall, though I didn't use FF because I'm used to specific things on Chrome. Moreover, most of the sites I work with do not trigger these issues on Chrome, in fact, it happens with only one site. PD: the site that triggers the issue on Chrome Dev Tools has lots of CSS variables. Not sure if that is related. UPDATE 1 WEEK ago I was able to use Chrome without issues even in the mobile view by disabling the option "Show media queries"
Go to the network tool and change it without any restrictions. Sometimes this happens if you change mobile settings. Google chrome changes this setting to test mobile device on low internet connection and leaves it that way.
Chrome not loading website when Google Fonts are installed/running
I have a website that's using the Open Sans typeface from Google Fonts. Now for some reason, when I have Open Sans running (either by using the embed codes provided on the Google Fonts website or by using #type-face to store the fonts locally) the site will sporadically fail to load at all. It may load the first time you get to the site but if you try to refresh the page it stalls and you have to close the tab to proceed. This ONLY ever happens in Chrome. I've been working on this issue for a whole day now and I've come to my wit's end. Any ideas would be hugely appreciated. Let me know if further info is needed. I'm using OSX version 10.9.2 and Chrome version 35.0.1916.153 Cheers.
chrome based browser "feature" - how to get original functionality back?
If you try to visit the default rss feed for any recently updated wordpress site in the chrome browser you ALWAYS get this annoying prompt for "Which service should be used for viewing?". This did not used to happen in chrome. This does not happen in other major browsers. How can I correct this in chrome to just show me the parsed xml like it used to? PS the example page you see in the background is http://wordpress.com/feed - as soon as you try to visit that page in chrome you should see this prompt as well.
I just discovered "Feed Intent Viewer" which is a Chrome extension that basically brings back the old functionality. https://chrome.google.com/webstore/detail/oceapojkdgeophkjdijkpbjifdnfimdh
I am using chrome Version 21.0.1180.79 on ubuntu and having the same request to download issue on such safe websites as sciencefriday.com. I have submitted the problem to chrome. -fingers crossed for a patch-
I found a solution after many research (because it's really annoying...) Download and install the new Beta version of chrome: it's all fixed
Can I use Chrome to debug why a Truetype font fails to load
I am trying to use a ttf font in a webpage and it is failing. The log tells me it failed to load but not more details (like why). I can use the font and Open it on my Mac. Any ideas on how I might debug the issue (ie find out why the font fails) in Chrome?
The Google Chrome inspector should tell you some information about it, on the Network tab chose the font tab on the bottom and then reload your page.