We have some software that uses a Chrome Extension to automate the browser (to crawl client web sites).
Usually we run several instances of this software in multiple tabs (up to 5) to parallel up work.
In Chrome 28 (beta) we have noticed that the inactive (background) tabs seems to be heavily throttled or running at a significantly lower priority. Benchmarks show that our extension is now running around 10 times slower in an inactive tab than when in the active tab. A similar behaviour is also seen in the active tab if Chrome is minimised.
This behaviour is not seen in Chrome 27 (stable) where the performance in active/inactive tabs is comparable.
Any thoughts or ideas would be greatly appreciated.
Our Chrome beta is (Version 28.0.1500.29 beta-m) running on Microsoft Windows 7 and Server 2008.
thanks
richard
On newest Chrome 55, this 'problem' (or maybe call it 'feature'?) still persists.
I've reproduced this problem on my build-page (runs lots of tests of an Ember application via QUnit) and on the background they take much longer. As #apsillers reported on a comment, this has been reported on another thread Javascript performance when running in an unfocused tab
Related
We Azure DevOps Server 2020 on-prem. And I noticed that I cannot open more than just a few Azure DevOps builds in different Chrome tabs concurrently. Namely, here is what I am doing:
Navigate to an Azure DevOps build and wait until all the details are loaded.
Repeat step (1) for another build
What I have noticed is that after 5-1 tabs (sometimes I am "blessed" with 5 fully loaded tabs and sometimes I cannot have more than 1) no new tabs are able to load the build details. I am using builds as an example, could be PRs or other screens.
At first I thought we have some concurrency limit on the server, but we do not. Neither IIS nor the Sql Server serving the requests have any concurrency limit defined. But then, I have discovered an even weirder thing - this concurrency limit exists in Chrome and Edge, but not IE!
I do not want to make IE my default browser, I would prefer keeping Chrome. But this drives me crazy.
My current theory is that it has to with signalr. Azure DevOps frondend uses some kind of signalr implementation. Maybe Chrome and Edge are too "advanced" to handle it correctly? Or maybe IE does not handle it at all and so Azure DevOps server fallsback to something IE supports and as a result no throttling is experienced?
I am pretty lost here and have no idea how to troubleshoot it further. Any ideas?
EDIT 1
Initial inspection of the URLs visited from chrome vs IE shows a difference in signalr urls:
IE: transport=webSockets
Chrome: transport=serverSentEvents
Does it make sense to anyone? Could this difference explain why Chrome is unable to open more then 1-5 (1 sometimes happens in the evenings) tabs serving Azure DevOps Server 2020 web pages?
EDIT 2
Right at this moment the limit is 6. I have 6 tabs open on the same exact build, 7th is hanging. The Network tab in the browser shows it is being stuck on the very first server side request to http://theserver:8080/tfs/DefaultCollection/SharpTop/_build/results?buildId=1184073&view=logs&j=ca395085-040a-526b-2ce8-bdc85f692774. No response at all. But if I close any of the other 6 tabs, it would load immediately.
EDIT 3
Posted on the MSFT Dev Community site - https://developercommunity.visualstudio.com/t/unable-to-load-more-then-6-sometimes-less-tabs-of/1466416
Hi it could be some product issues around the supported browsers with policy/configuration on how http/https would handled, suggest you open up issue in the Azure DevOps Developer Community , and MS PG/support team can dive in to feedback you.
the similar has opened Azure DevOps Server not loading properly that close to your descriptions here.
When I run the chrome performance tool, most of the time I get a very shallow stack shown. So it's impossible to debug anything.
It doesn't happen on my work machine but does on my home machine (also on a friends machine with the same config):
Windows 10 Pro - Version 10.0.18362 Build 18362
CPU ryzen 7 3700x
Chrome Version 78.0.3904.108 / Beta / Canary
Sometimes if I use CPU throttling it shows the proper stack but the vast majority of times it does not. Am I missing a feature toggle somewhere?
Is someone else running into this?
Thank you.
Larger screenshot:
Try using chrome stable version.
Canary is simply a much newer release that's not as well tested. I have debugged this page in my chrome (version: 78) over 10 times with 6*CPU throttling. I got stack over 10,000 ms all times.
You can get more information about performance tab in this official link.
So i have the following problem.
Any time i click on a request to view the headers/payload/response
i receive a not responding window.
If i wait ~2 minutes it works.
So what i receive here is a developer tools not responsive status when working on local machine.
I tried to re-install chrome. Nothing changed.
Current Version is: Version 50.0.2661.102 m listed as up to date.
Is there any possibility to get some logs or did anyone faced the same problem?
I think it can be relevant if i show what extensions i have installed.
But i tried to enable/disable them and nothing changed.
And i get the same comportment in incognito mode too.
Later edit: I somehow identified the problem. Idea is that chrome is trying to display the cookie (request headers) which was 18k characters long and it looks like this is slowing a lot developer tools and sometimes make him crash.
I just saw that in Mozilla cookies are limited to a couple of characters (display perspective) and after that they show ...
I can't find any known issues regarding this crash, so here are a couple of steps you could take:
Use the Chrome Cleanup Tool and see if that helps.
Fully clean and re-install Chrome (including deleting user folders). If it works after that, you can slowly add extensions and plugins back and see if any reintroduce the problem.
I am trying to record with Chrome in LoadRunner for the first time (having to record a mobile app through an emulator that only works in Chrome), but when recording with Web (HTTP/HTML) protocol in Chrome I only get empty actions, no events are recorded (tried with several "standard" web pages).
LoadRunner opens Chrome fine, I click a few links and then stop recording, but script actions remain empty. Using HTML-style recoring.
Setup:
Windows 7 64 bit SP1
Loadrunner VuGen v11.52
Chrome v27.0
I have colleagues that manage to record fine with similar (if not exact same) setup. Has anyone faced the same issue?
You must close all Chrome windows before starting recording and use only the window that VuGen opens to record. Also make sure no chrome processes running before recording.
Why not record the actual device with vugen instead of an emulator?
Keep in mind you are trying to use a 32 bit application to record a 64 bit application. I would even go so far as to recommend that you look at using the proxy model recording as an HTTP proxy for the "old recording engine."
this morning I noticed my Chrome updated to Chrome 22 and that the search in the top right has been removed and can now be accessed with ctrl-f.
I also noticed that ctrl-shift-f is no longer working as expected... (but this is inconsistent)
The global search has been a huge time saver for me, and now sometimes it doesn't work until I've viewed a script at least once.
For example, I have 5 scripts that I know all contain "fn_init"
I search for fn_init and nothing comes up.
I open one of those scripts and then ctrl-shift-f again, and finally get a matching result for just the one file...
Is this working as intended? Am I missing an option or something? My dev tools config options are:
General
Disabled cached
Sources
Show folders checked
Search in content scripts checked
Also: how can I install an older version of Chrome and stop it from updating automatically?
To get an older version of Chrome your best bet is to find a build of Chromium from https://chromium-build.appspot.com/p/chromium/console however if this if for devtools stability you are missing out on a lot of new features and bug fixes.
As for Search across all files it is still there and CTRL-SHIFT-F on Windows and CMD-OPT-F on Mac. See Addy Osmani's post https://plus.google.com/115133653231679625609/posts/e4W2kdrFJY9
If you find issues as bugs, it is better to raise the issue on http://crbug.com/new as it will get direct attention from the engineering team there.