1338309 - Gmail complains that cookies are disabled in e10s windows

Status: RESOLVED WORKSFORME

(Core :: Networking: Cookies, defect, P2)

Description

[Ethan Glasser-Camp (:glasserc)]

I just switched to Nightly for my main browsing and I can't log into Gmail, either with my personal or my corporate account. I get redirected to https://mail.google.com/mail/u/0/?view=nocookies . I'm able to log into calendar.google.com. I'm also running the Self-Destructing Cookies add-on, but I have google.com whitelisted, and even when I disable the add-on, I get the same behavior.

Opening a non-e10s window allows me to log into Gmail correctly.

Comment 1

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

I can sign in to gmail on yesterday's Nightly with e10s enabled. I'm on Windows 10, and Firefox is set to use more than 2 content processes. I'll update to today's Nightly and see if something breaks.

Comment 2

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Nope, current Nightly signs in just fine, too.

Wondering if it's a sandboxing thing, since you're on Linux?

If you switched to Nightly, are you using the same profile that you used for release Firefox? Maybe permissions for the cookies database changed in some incompatible way. Try clearing all of your cookies, or launching Nightly with a new profile?

Comment 3

[Ethan Glasser-Camp (:glasserc)]

Attachment: permissions.sqlite

Comment 4

[Ethan Glasser-Camp (:glasserc)]

I already tried clearing just Google cookies, and that didn't seem to fix it.

Running Nightly with a new profile seems to work OK (lets me log in to Gmail without problems).

Going back to the old profile and using the Prefs "clear recent history" to clear "Everything" from "Cookies" doesn't resolve the problem.

Doing `rm /path/to/cookies.sqlite` doesn't seem to resolve the problem.

By copying over individual files from the old "broken" profile and the new "working" profile, I was able to narrow it down to `permissions.sqlite`. Removing it from the profile causes the profile to start working, and putting it back causes it to break. I've attached the file.

Before switching to Nightly, I think I was on 50.1.0. I'm not sure if jumping to 54 was too big a jump :)

Comment 5

[Honza Bambas (:mayhemer)]

sqlite> select * from moz_perms where origin like '%google%';
1|https://mail.google.com|plugin-hidden-notification|2|0|0|1480460791343
4|http://google.com|cookie|9|0|0|1485461043553
5|https://google.com|cookie|9|0|0|1485461043558

What permission is 9?

Comment 6

[Ethan Glasser-Camp (:glasserc)]

I believe it is ACCESS_ALLOW_FIRST_PARTY_ONLY: https://dxr.mozilla.org/mozilla-central/source/netwerk/cookie/nsICookiePermission.idl#33. From looking around a little bit at the code, it seems the Self-Destructing Cookies add-on uses this value (among others) as part of its whitelist for domains that can leave cookies that survive the closing of the browser tab.

Comment 7

[Dragana Damjanovic [:dragana]]

Is this a problem of Self-Destructing Cookies add-on? Is it working if you disable it?

Comment 8

[Ethan Glasser-Camp (:glasserc)]

No, as I wrote in comment #0, disabling the add-on does not by itself fix the problem. However, I do think the add-on is responsible for putting the permission in `permissions.sqlite`.

Comment 9

[u408661]

Does that restriction stay in the permissions table if you disable self-destructing cookies? If so, what happens if you leave the add-on disabled *and* remove those restrictions manually?

Comment 10

[Ethan Glasser-Camp (:glasserc)]

Yes, all restrictions in the permissions table remain even when you disable the Self-Destructing Cookies add-on. This is why I still couldn't log in to Gmail in comment 0. Removing the restrictions manually is enough to let me log in to Gmail, regardless of whether or not I disable the plugin.

Comment 11

[u408661]

Well, this is fun. Sounds like there's a couple issues here. First, seems like self-destructing cookies should be removing the restrictions it adds when it's disabled/uninstalled (do add-ons even have the ability to do that?).

But there definitely seems to be a necko and/or permissions issue at hand, since this only happens in e10s windows. Jason, don't we have some people in Taipei that have been poking at cookies lately that might be able to dig into this more?

Comment 12

[Shian-Yow Wu [:swu]]

Amy, please take a look at this issue, thanks.

Comment 13

[ymerlin]

I have the same problem as the comment 0 after I manually enabled e10s after I installed firefox 53.  I tried several tweaks:

1. disable self-destructed cookie addon, not working
2. safe mode, not working
3. refresh firefox, working without e10s enabled by default, not working with e10s enabled
4. manually add https://google.com to whitelist of self-destructed cookie with allow all option <----working!

I did not test refresh firefox without self-destructed cookie installed.  Hope my report would help.

Comment 14

[Amy Chung [:Amy]]

Hi Ethan,
I can't reproduce this issue, and my reproducing steps as below:
1. Used firefox 54.
2. Installed Self-Destructing Cookies add-on.
3. Opened e10s.
4. Tried to log-in gmail.
Would you help me to confirm the steps?
And does the behavior of this bug also occur on nightly 56?
Thanks!

Comment 15

[Ethan Glasser-Camp (:glasserc)]

Hi Amy, this behavior stopped happening for me at some point but I don't know when. Using Nightly 56, this behavior doesn't occur, possibly because the Self-Destructing Cookies add-on is not e10s compatible. I checked `permissions.sqlite` and it seems like the google.com `cookie` rows are gone. I'm not sure what (if anything) this means. As far as I'm concerned, I guess this can be closed.

Comment 16

[Amy Chung [:Amy]]

Ok, Thanks!