Chrome + gmail high network outbound traffic at startup - google-chrome

I'm fighting against a strange behavior in our office network.
Every morning when we switch on our computers, our network was overload on outbound traffic.
After several test I found a possible cause.
I noticed that when we start Chrome (and gmail?) there is a high traffic generated from my computer to Google servers (e.g.: 74.125.133.132). Here a resource monitor screenshot:
The network traffic doesn't go down until I stop chrome and I start it again.
No extensions installed and every possible traffic generating feature is disabled.
Monitoring the network and restart Chrome every morning is quite annoying. Does someone have a similar behavior and a solution/workaround?

On start up chrome checks weather new update or fixes are available or not..
Or you might be having an chrome extension like _toolbar type, these type of extensions causes a lot of traffic..
Go to settings => extensions => and disable unnecessary and unrecognized extensions..
Hope it solve your problem..

Related

Fiddler capturing traffic from a specific process stopped working in Chrome

Open Chrome and navigate to google.com
In Fiddler use the "Any Process" button to select that Chrome tab
In Fiddler the "Any Process" button changes to something like "chrome: 11788"
In the Chrome tab search for something
I expect traffic to be captured by Fiddler but no sessions are displayed. If I use "Any Process", traffic is captured from all applications.
The "Use Filters" checkbox is unchecked in the Filters tab.
I uninstalled and reinstalled Fiddler.
I have the latest version installed.
What else could I do?
Modern versions of Google Chrome use separate process for making requests; so the process of the main window, detected by the 'Any Process' tool, is different.
The team is considering a fix, but it is currently not implemented, see "Target Any Process" feature no longer working with Chrome.
Possible workarounds meanwhile are:
Use other filtering functionality - e.g. capture a request from Chrome, and from the Sessions view choose right click -> Filter now -> Show only process=<process number>.
Filter everything else. In Fiddler, uncheck Tools -> Options -> Connections -> Act as system proxy on startup. Then Start Chrome with manually specified proxy settings, pointing to the port on which Fiddler is listening:
chrome --proxy-server=http://localhost:8888
This way the only captured traffic will be from this instance of Chrome.
Detailed version: Why Fiddler's Process Picker tool doesn't work with Chrome anymore
Brief version: For security and performance reasons Chrome now handles network requests through a separate network service. So when you are pointing the 'Any Process' tool of Fiddler on any Chrome window/tab, you are actually pointing to the UI (browser process) of Chrome browser.
There is one quick workaround for this:
Navigate to chrome://flags/#network-service-in-process in your Chrome browser. You would see Runs network service in-process and its value would be set to Default.
Change the value from Default to Enabled. By doing this you are telling Chrome to handle network requests from the browser process which also handles the UI.
Restart Chrome. You should now be able to capture network requests by pointing the Any Process tool on any Chrome tab.
Once you are done with your development activities do not forget to set the flag back to Default. This would give better performance.
NOTE: At the point of writing this, I am using Chrome 84.

Fiddler suddenly cannot capture anything from broswers

Fiddler had worked well on my laptop, but all of a sudden it cannot capture anything from my browsers. I have no ideas about what I have done may cause this problem.
The version of my fiddler is v4.6.0.5, it cannot capture http requests from all of my browsers, chrome, IE and Edge. My system is Windows 10.
I've carefully read the webpage Fiddler not capturing traffic from browsers
However, solutions works well for others do not work in my situations.
I've tried reinstalled fiddler and reset chrome hundreds of times
http://localhost.fiddler:8888/ cannot be found
http://127.0.0.1:8888 returns "This page returned a HTTP/200 response
Originating Process Information: chrome:79748"
I didn't use any filters
I have no extensions on chrome and close all kinds of VPN software.
I've checked 'Decrypt HTTPS traffic'
Anybody knows how can I solve the problem? Thank you!
I found that some of the software's http request is captured. It seems like that only the browsers' requests are not captured.
I temporarily use the developer tools in chrome for replacement(Ctrl+Shift+I, choose "NetWork"). It can capture the requests missed in Fiddler.
Your output indicates that:
Fiddler is running, and
It isn't blocked by a firewall or other software
Fiddler is not set as your system's proxy
On Fiddler's File menu, does the Capture traffic item have a checkmark next to it? While Fiddler is running, if you click Tools > WinINET Options > LAN Settings, what do you see?
Do you have any third-party antivirus software installed? Is this machine under the control of Group Policy (e.g. on a corporate network)?
If you start Chrome like so: chrome --proxy-server=http://127.0.0.1:8888, what happens?

How can I debug an indefinite HTTP request in Chromium/Chrome?

I am troubleshooting an issue where I believe an HTTP request is waiting an indefinite amount of time for a response. In Chromium's developer console, the Network tab does an excellent job at displaying completed traffic and events, but not current ones (that I can see).
How can I debug a lingering HTTP request using Chromium's developer console?
I have had the same issue for quite sometime. On the developer tools Network tab, I can see that all requests match the response on my server log and none is waiting. I even tried to shutdown the server while it is happening, and it still waits indefinitely.
This doesn't happen with Firefox and Opera so I'm inclined to say that it's a chrome bug.
Added: I have also noticed that when I close chrome then open it again, the issue disappears.

google hangout microphone is not working with network error and firewall setting issue

From last 1 week i am facing strange issue in google hangout. as i join a meeting first a message pops up
Your microphone is not working or is hardware-muted!
then after few seconds i see message
Couldn't start the video call because of a network error.
Please check your firewall settings and try again.
with button to try again. and it keeps going on in this way.
I have checked firewall settings
I have tried with different networks
I have tried with different computers
I have tested microphone and speakers they are correct
I inspected ajax calls in firebug and i see this
NetworkError: 404 Not Found - https://plus.google.com/u/0/talkgadget/_/ping?id=1
NetworkError: 404 Not Found - https://plus.google.com/u/0/talkgadget/_/ping?id=2
POST https://plus.google.com/hangouts/_/channel/bind?...200F2A8A372&RID=67018&AID=84&zx=2a53yvv7e45w&t=1 Aborted
At google Community somebody answered like this:
I have found the culprit. I use Spybot Search & Destroy's Anti-Beacon software to block telemetry data that Windows 10 constantly sends to Microsoft. This is why trying multiple Windows 10 machines that I have configured did not alleviate the problem. Somehow one of the IP block entries it adds to the Windows Firewall now conflicts with Google Hangouts. I will report this to the software vendor.
Source: https://support.google.com/hangouts/forum/AAAAfpFnBZ8mdNNg8LNvNg/

Ripple emulator chrome plugin is taking long time to execute

I was using Ripple Chrome extension for test running my phonegap apps, and I did all settings for Ripple, like making a Chrome shortcut with --allow-file-access-from-files and in Chrome extension list checking "allow local file access" for Ripple.
On running my HTML file which I made for phonegap build, Chrome is taking a good time to deliver a response. Everything is working, the only issue is the delay on response.
I tried on another desktop, and there it is quiet and fast. I re-installed the extension and restarted Chrome and OS a couple of times to no effect.
For your information, I had similar issues when using Chrome. Make sure Chrome isn't running in the background when you close it. Since a few versions of Chrome, this is enabled by default. Check your taskbar to see if this is the case.
If Chrome is indeed running in the background, right-click on the chrome-icon in the taskbar and disable "running in background". This worked for me and now Ripple fires superfast.
You probably need to confirm your system spec. development workstations are known to be resource demanding, particularly the RAM, and processors. if your app was faster on another system, you might want to check that system's spec also and compare with yours.