New issue
Advanced search Search tips

Issue 626975 link

Starred by 4 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

After some time of the incognito mode something happens to cookies so that Gmail and Twitter mobile websites fail to work

Reported by sogryz...@gmail.com, Jul 11 2016

Issue description

Steps to reproduce the problem:
1. Run Chrome 40.0 on Android 4.4.2 in the incognito mode.
2. Open Gmail's mobile website in it.
3. Work with Gmail for I few minutes.
4. See it goes "offline" and/or reports "cookies problem" and fails to continue.

What is the expected behavior?
Regardless how much time I use Chrome in its incognito mode it does not cause any "cookies problem" and my Gmail/Twitter mobile websites continue working.

What went wrong?
As I said above, Gmail/Twitter go "offline" and/or report "cookies problem".

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 40.0.2214.89  Channel: stable
OS Version: 4.4.2; 4027D Build KOT49H
Flash Version: N/A

No.
 

Comment 1 by sogryz...@gmail.com, Jul 11 2016

See the 2 screenshots attached - they display the result of the problem. Sorry for they're in Russian only. :-)
Screenshot_2016-07-11-09-04-46.png
37.4 KB View Download
Screenshot_2016-07-11-09-05-42.png
98.2 KB View Download

Comment 2 by droger@chromium.org, Jul 12 2016

Chrome 40 is an old version, does this happen on version 51 (current stable) or newer?

Comment 3 by sogryz...@gmail.com, Jul 13 2016

I have upgraded my Chrome to the version 51.0 (see the screenshot attached), tested and met the same problem. :-(
Screenshot_2016-07-13-12-11-59.png
49.1 KB View Download

Comment 4 by mge...@chromium.org, Jul 19 2016

Components: Internals>Network>Cookies
Status: Untriaged (was: Unconfirmed)

Comment 5 by mmenke@chromium.org, May 23 2018

Status: Archived (was: Untriaged)

Comment 6 by sogryz...@gmail.com, May 27 2018

Why my issue was archived? It's still NOT resolved on my Android 4.4.2. :-(

Sign in to add a comment