Clicking on "Cookies: x in use" crashes OSX desktop and leads to OSX user login
Reported by
michael....@dswiss.com,
Jun 28 2017
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Open a website which sets at least 1 cookie 2. Click on the ribbon next to the URL to reveal site settings 3. Below "Cookies" click on "x in use" What is the expected behavior? Show cookies in use What went wrong? OSX crashes and shows user login prompt again Did this work before? Yes not sure (approx. 2 months ago ~ April 2017) Chrome version: 58.0.3029.110 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 26.0 r0
,
Jun 28 2017
Side note: It also happens when clicking on cookie informations called "Show cookies and other site data" when visible in the URL bar. So I suspect something broken in the cookie handling. I also reinstalled Chrome and used a new profile to check for the issue and I could reproduce that as well.
,
Jun 29 2017
Tested on Chrome Stable #59.0.3071.115 and reported Chrome #58.0.3029.110 on Mac 10.12.5 and unable to reproduce the issue. Please refer the screen cast attached. @michael.tanner -- Could you please try updating your Chrome to latest stable version as mentioned and provide us the update. If you still see the crash, kindly provide the Crash ID by navigating to chrome://crashes. Could you also please provide the sample URL for the case mentioned in Comment#2. Please let us know if we have missed anything. Thanks in advance.
,
Jul 6 2017
[MacTriage] It sounds like the windowserver is crashing as a rsult of displaying the cookie dialog. Perhaps related to that dialog's shadow?
,
Jul 7 2017
Are you using vmware or some other kind of non-Apple-standard hardware? I suspect this is related to Issue 515627 Do you have any WindowServer crashes listed under Reports when you run Console.app ? (if so, can you attach one of those? - that will help us investigate further)
,
Jul 7 2017
I'll have a look for the logs later. I use standard Apple hardware btw and I already use the latest Chrome.
,
Jul 7 2017
Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11 2017
,
Jul 13 2017
michael.tanner@ could you please respond to the comment #3.
,
Aug 10 2017
[MacTriage] Closing out for lack of response for over 30 days. Please reopen if you can provide the requested info.
,
Aug 14 2017
I was abroad and didn't have a lot time to review the report. I tried to trigger the bug again and I was unable to produce a screencast as the issue seems to have disappeared. I think we can close this as it doesn't happen again. If it occurs again I will think about recording more details and maybe re-open the bug report if possible.
,
Aug 15 2017
I could reproduce and screencast the behaviour and I have much more information on that case. I'll open a new bug report with accurate informations and the screencast. I think this is more appropriate. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by nyerramilli@chromium.org
, Jun 28 2017