I'm getting this console notice in Chrome Devtools while developing on localhost:
Active resource loading counts reached a per-frame limit while the tab
was in background. Network requests will be delayed until a previous
loading finishes, or the tab is brought to the foreground. See
https://www.chromestatus.com/feature/5527160148197376 for more details
I tried disabling the "Throttle expensive background timers" flag here but that didn't work. The link provided in the console message doesn't say how to disable/override.
This question might be asking the same thing but I'm not certain.
Does anyone know how to override this setting in Chrome? I'm running Chrome Canary 72.x on Mac.
Via the Chrome team, set Enable Resource Load Throttling to disabled:
chrome://flags/#enable-resource-load-scheduler
Related
for debugging my application I need some test on chrome Time Out Error page. but it frequently auto-refresh in the new version of chrome.
I want to disable auto-refresh on Time Out Error pages on chrome.
Previously it was possible to disable this by changing settings of Enable Offline Auto-Reload Mode and Only Auto-Reload Visible Tabs in chrome://flags/
like described in the accepted answer here: Disable Chrome Auto Reload on Time Out Error
Unfortunately, those flags are not available anymore.
Does anybody know a solution to this?
Would appreciated help on a gap in comprehension. Sending push notifications to Chrome running on a Windows 10 machine (tried on older Windows also) results in the notifications popping up only when the Chrome browser is open (similarly for installing the page as a PWA). On numerous sites and posts it says that Chrome can run a background process even when the browser is closed and still receive notifications that will kick off the browser or the PWA.
Have reviewed a number of posts from back in 2015/2016 which don't appear relevant based on current state of service workers, PWAs. Have also looked at the W3C spec and Chromium post on design and architecture which don't really seem to cover how the host OS (e.g., Windows) invokes the browser.
The Chrome browser is set to run in the background (setting->advanced->Continue running background apps when Google Chrome is closed) but on closing Chrome and looking at the running processes on the system, there does not seem to a Chrome background thread running (i.e., it does not seem that Chrome inherently runs some background process). Push notifications (e.g., sent via OneSignal) which result in the appropriate page being opened when Chrome is already open or the PWA receiving the notification (we are currently using GCM not FCM if that makes a difference) if it is open, do not seem to kick off the chrome browser if it is not already running. Otherwise the notifications are processed correctly.
From the google developer site and OneSignal documentation, etc, I had somewhat assumed (apparently incorrectly) that having a service worker for push notification would somehow create a background process environment.
So, the question is, what is required to keep Chrome running in the background to be able to receive the push notifications? Can it be done with a service worker? If the code is in a PWA is that different? Is a Chrome extension required? though having to create an extension would seem contrary to the point of creating the service workers and making the app a PWA.
I note also that it posts indicate that with Firefox this is not possible as Firefox completely exits on close with no background processes.
Any thoughts would be appreciated.
I am intercepting and returning a resource from service worker cache. It takes around 300-400ms to download the content as per Google Chrome devtools. I checked in Firefox, the download is instant.
I expected that download time to be a lot smaller since no network is involved. I intercept the fetch with the usual match function:
event.respondWith(
caches.match(event.request).then(response => response)
);
Is there something wrong I am doing in the way I intercept and return the resource from cache?
You can try the following solutions from this google forum:
Delete your cache and cookies
Use incognito mode If this helps then temporarily disable your extensions to identify which one is causing the rendering problem. To
do this go to chrome://extensions and uncheck Enabled for each
extension one by one.
Reset your browser settings
Turn off hardware acceleration by going to Menu > Settings > Advanced Settings > Under 'System' uncheck Use hardware acceleration
when available.
I'm trying to use the Chrome DevTools Network viewer to inspect WebSocket frames. I'm not sure if i've discovered a bug or something i'm doing wrong. Essentially, while inspecting the frames, whenever a new frame is recevied, the Network viewer jumps away/deselects the websocket connection. It is particularly bad when there are "ping" type messages being sent every 5-10 seconds, as this makes it almost impossible to keep the frames tab open.
My Chrome version is 58.0.3029.110 (64-bit)
Steps to reproduce:
Hit F12 to open DevTools
Navigate to http://www.websocket.org/echo.html
Check "Use secure WebSocket (TLS)" and click Connect
In DevTools, goto the Network tab and find the websocket connection for the chat (wss://echo.websocket.org/?encoding=text), select it and view the Frames.
Click Send on the page to send a message.
The "?encoding=text" websocket item in the network list will deselect itself and the frames view is gone!.
Any ideas?
I have found a workaround which you can make use of till this bug gets fixed.
Apply search filter to get the required websocket request alone as the displayed item, now the selected blue bg will get hidden but frames tab will not get closed.
Useful filters:
is:running will show currently active websocket request.
domain:requireddomain.com will filter required domain
Looks like this is a bug, as others have reported the same issue here.
I'm trying to simulate a slow connection in Chrome so that I can see how my application behaves under slow speeds. I've downloaded and installed Fiddler 2, and I can run it at the same time as Chrome. When I look at the logs in Fiddler, it captures my start page, being google.com, but it then fails to capture any subsequent requests I make within Chrome, even omitting searches from the same page it started up with. The Fiddler setting to simulate modem speeds also has no effect on Chrome at all. I can close Chrome and re-open it, and the start page will again be captured, but nothing beyond that. It captures from IE just fine, and it even captures the traffic from Desktop Earth trying to retrieve cloud data, but no dice within Chrome.
I have looked at this question, and it has three answers but none selected. The third one has this code:
ChromeOptions options = new ChromeOptions();
options.AddArgument(string.Format("--proxy-server=http={0}:{1};https={0}:{1}", proxyHost, port));
driver = new ChromeDriver(options);
...but I have no idea where I would it, as I am completely new to Fiddler. Can someone help me out?