Google Chrome Resolving Host (1Password causing slow internet)
Hi guys
Been suffering slow internet recently despite good ping (10m/s) and download speed (60MBPS). Chrome was 'Resolving Host...' for a loooonnnggg time.
Did the usual stuff like resetting router etc.
Next step, reset Chrome settings to see if an Extension is causing it.
Went through Extensions one by one, and it is 1Password that is the culprit. On disabling it, internet was back to being mega-fast.
Has anybody else experienced this? It is a recent phenomenon for me. 1Password team, are you getting Support Tickets to this effect? Any advice?
1Password Version: 5.3
Extension Version: 4.4.3.90
OS Version: OS X 10.10.5
Sync Type: Not Provided
Comments
-
Sorry @madcap, this is the first report I've heard of. While it doesn't mean it isn't possible you'd expect quite the spike if this were a general issue.
- Do you run the 1Password Chrome Extension in multiple profiles that are open concurrently?
- Does the issue return if you have all extensions disabled but 1Password? In other words can you reproduce the issue with just our extension loaded in Chrome and no other.
- Do you run any form of firewall, anti-virus, parental control, VPN or proxy software? I'm wondering if we're seeing some sort of interaction when the extension is enabled and something that actively monitors all incoming and outgoing packets.
Hopefully something might come from these questions :smile:
0 -
Hello
- No
- Yes
- No.
0 -
Greetings @madcap,
Well I'm baffled as in completely perplexed. We're hearing no other reports and it seems like it's happening on a pretty regular setup.
Maybe a diagnostic report may shed some light.
I would like you to create a Diagnostic Report please. This guide will assist.
Please do not post your Diagnostics Report in the forums
The email address you will want to use is support+forum@agilebits.com.
When sending the diagnostic report to the address above it would help immensely if you could include a link to this thread and your forum handle so we can connect the two.
Once you've sent the report a post here with the ticket ID will help us to keep an eye out for it. With access to the report we should be able to better assist you :smile:
0 -
Greetings @madcap,
I've just come across another post on this but by the time I stumbled upon it the user was already reporting that a simple reboot of the Mac solved the issue. You mentioned rebooting the router, did you try the Mac?
0
