Chrome extension crashes Google Inbox

mathcolo

Hi everyone, I'm on Chrome 40.0.2214.93, OS X 10.10.2, 1Password client 5.1, and extension version 4.2.5.90. I cannot pinpoint exactly how long this has been happening, but loading https://inbox.google.com with the 1Password extension enabled causes Chrome to throw an "Aw, Snap!" error. I've determined it's the 1Password extension causing the problem, because disabling all extensions allows the page to load properly, and re-enabling the extension breaks it.

Interestingly, refreshing the page once allows Inbox to work properly. The issue comes back when I attempt to open Inbox in a new tab or window.

I've tried reinstalling the 1Password Chrome extension and wiping my Chrome user profile entirely. Any ideas?

Megan

Hi @mathcolo,

I'm sorry to hear that you're having trouble here. We've done some testing here and everything seems to be behaving as expected. Could you please provide us with the exact steps that you take to load the website? For example: do you go to the URL and then invoke the extension to fill your details or selecting the Login directly from the extension (so 1Password opens the URL and fills your details)?

Is there any further text with the "Aw, Snap!" error that could help us determine where things are getting tangled up?

Thanks for helping us track this down - the more detail you can provide, the more quickly we'll be able to find a solution.

mathcolo

Hi there, I'm glad it's working for you all at least! In terms of exact steps, well:

1. New tab
2. Enter URL, https://inbox.google.com
3. Get "Aw, Snap" error immediately without touching the 1P extension whatsoever.
4. Refresh with Command-R, Inbox loads.

Unfortunately the error page doesn't display anything else that could be helpful. Screenshot: https://dl.dropboxusercontent.com/u/127328/chrome-crash-1p.png

Should add, it's a bummer, nothing in Console.app seems relevant.

Any other ways I can help figure this out?

Drew_AG

Hi @mathcolo,

If you're simply entering the URL and immediately get an error, I'm not sure how the 1Password extension would cause that. If I understand your initial message, it works when all Chrome extensions are turned off, and gives an error when only the 1Password extension is enabled? If so, please try disabling the 1Password extension and re-enabling the rest of your Chrome extensions, then try entering the URL again. Does it work, or does it give you the error?

If it works when all Chrome extensions are enabled except for 1Password, please try installing our latest beta extension to see if it helps:

• Open the following link in Chrome: https://agilebits.com/onepassword/extensions
• Click the link for Enable betas (underneath the Install button)
• Click the big green Install button and follow any additional steps

Once you've installed that, restart Chrome, then try the URL again. Does it make any difference? Let us know how it all goes, thanks!

mathcolo

Hi again,

My apologies for the typo in my original message, I shouldn't have said that it works only when I disable all extensions. In reality the only difference in the crash occurring or not is whether the 1Password extension is enabled or not. So indeed, when I disable the 1P extension and all the rest are enabled, it works properly.

I just followed your instructions and installed the beta extension. I disabled the non-beta extension and all other extensions, and the crash still occurs :neutral_face:

MikeT

Hi @mathcolo,

Does it happen in Safari or just in Chrome? We're trying to get it to crash but it is not doing so for us.

Since you were willing to wipe out your Chrome profile, would you also try installing Chrome Canary and see if it happens there too?

Also, do you have the 64-bit version of Chrome 40?

mathcolo

Just tried in Safari and it didn't happen there (although I should note that Inbox doesn't fully load over in Safari, so...eh). I also just installed Chrome Canary and I was unable to reproduce it there either.

And yes, I do have the 64-bit version of Chrome 40.

MikeT

Hi @mathcolo,

That suggests it is not really 1Password, it shouldn't be inconsistent like that.

When you did a wipe of your Chrome profile, did you also reinstall Chrome 40? If not, can you try doing a full reinstall and see if it works.

mathcolo

Hi @MikeT, my apologies for not getting back to you immediately.

I just went ahead and wiped Chrome entirely from my machine. I deleted

• Google Chrome.app
• Google's folder in ~/Library/Application Support
• com.google.Chrome.plist in Preferences
• Anything else I could find

I then redownloaded Chrome stable and the 1Password extension, and the problem is still present. Anything else to try?

Unknown

This content has been removed.

rickfillion

Hi @mathcolo,

I too have tried to recreate this, using Chrome 40.0.2214.94 (64-bit), 1Password Extension 4.2.5.90 on OS X 10.10.2 and have not had a problem.

The 1Password app itself shouldn't be part of this equation, as the browser extension shouldn't communicate with the app at all until you either invoke the extension or the mini. We should be able to confirm this by having you quit 1Password and the mini and you should see the same results.

What other Chrome extensions do you have installed? I wonder if maybe it's not necessarily the presence of the 1Password extension that's causing this issue, but instead the presence of the 1Password extension and some other extension. I'd like us to try installing whatever extensions you have installed to try to more properly recreate your scenario.

Rick