Issue metadata
Sign in to add a comment
|
profile gone temporarily berserk
Reported by
teo8...@gmail.com,
Apr 16 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: There are no steps to systematically reproduce the issue. Here's what I did and what happened 1. Right after booting, I started Chrome and I got no error message of any kind 2. I tried to navigate to a few sites that I am usually always logged in, including Google, Facebook, and a couple more 3. I observed that I was unexpectedly logged out of most of them, as if my cookies had been deleted (which I hadn't), but not all. As far as I can tell, I was logged out of all https sites that I tried, but I was still logged in on the one that I tried that is plain http 4. I closed Chrome 5. I reopened Chrome, and I got an error message saying that there were troubles loading my profile (this happens almost systematically when I close Chrome and reopen it "quickly enough", isn't that pathetic?) 6. I closed Chrome, this time waited a little more, and reopen it, and got the profile error again. 7. I closed Chrome, and from a terminal, I ran "ps aux | grep chrome" What is the expected behavior? None of this should have happened starting from step 3. Anyway, at this point, after step 7, there should be no Chrome process running, obviously What went wrong? Pretty much everything. Anyway, at step 7, there were a bunch of processes running with "chrome" in the executable path So, I killed one of them. As a result, all of them "died". After that, I could start Chrome normally and NOW everything was working as expected. Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: Flash Version: unbelievable
,
Apr 16 2018
,
Apr 17 2018
Thanks for filing the issue! @Reporter: From your comment#0 and #1 it is understood that the issue has been resolved and everything is working fine, Could you please let us know if we can close the issue.
,
Apr 17 2018
> it is understood that the issue has been resolved I am not experiencing the problem anymore after restarting Chrome, but that doesn't mean the issue has been "resolved". You shouldn't close it unless you know what caused it and you know to be fixed and that it won't happen again. If Chrome crashed and after restarting it was working fine, would you call the issue "resolved" and close the bug report about the crash?
,
Apr 17 2018
(note that I'm forced to delete my comment and repost it corrected because this stupid system doesn't allow me to edit my own comment)
,
Apr 17 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 27 2018
,
Apr 27 2018
Note that the symptoms of this issue and those of 835817 are different as per https://bugs.chromium.org/p/chromium/issues/detail?id=835817#c8 I'm not saying it can't be the same issue, but have you checked thoroughly before merging? |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by teo8...@gmail.com
, Apr 16 2018