Searching or deleting cookies in chrome://settings/siteData causes crash
Reported by
ingo_bru...@web.de,
Dec 17 2017
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.24 Safari/537.36 Steps to reproduce the problem: 1. Open chrome://settings/siteData 2. Type something in the search field 3. or: Try to delete some cookies What is the expected behavior? What went wrong? Chromium sometimes crashes, especially when it is freshly started. So maybe there is some kind of race condition. This goes for some versions now. I do not know exactly when it started. Here is the stack trace: [1480:1480:1217/200142.904469:FATAL:settings_cookies_view_handler.cc(312)] Check failed: request_.callback_id_.empty(). #0 0x56189cb051fc <unknown> #1 0x56189cb1e8d1 <unknown> #2 0x56189eaf2f5b <unknown> #3 0x56189bad02ff <unknown> #4 0x56189bad0227 <unknown> #5 0x56189baa0d55 <unknown> #6 0x56189b7ff475 <unknown> #7 0x56189d01555b <unknown> #8 0x56189cb061fd <unknown> #9 0x56189cb2494b <unknown> #10 0x56189cb24ed9 <unknown> #11 0x56189cb2793f <unknown> #12 0x7f8a659bb5d7 g_main_context_dispatch #13 0x7f8a659bb7e8 <unknown> #14 0x7f8a659bb86c g_main_context_iteration #15 0x56189cb27805 <unknown> #16 0x56189cb4bcb4 <unknown> #17 0x56189c80c69b <unknown> #18 0x56189b6c9307 <unknown> #19 0x56189b6cc082 <unknown> #20 0x56189b6c55da <unknown> #21 0x56189c7e1bde <unknown> #22 0x56189c7ebec8 <unknown> #23 0x56189c7e0b24 <unknown> #24 0x56189afb219f ChromeMain #25 0x7f8a5cce545a __libc_start_main #26 0x56189afb202a _start Received signal 6 #0 0x56189cb051fc <unknown> #1 0x56189cb04d51 <unknown> #2 0x7f8a67aa1990 <unknown> #3 0x7f8a5ccf9e80 gsignal #4 0x7f8a5ccfbad0 abort #5 0x56189cb03915 <unknown> #6 0x56189cb1ebcc <unknown> #7 0x56189eaf2f5b <unknown> #8 0x56189bad02ff <unknown> #9 0x56189bad0227 <unknown> #10 0x56189baa0d55 <unknown> #11 0x56189b7ff475 <unknown> #12 0x56189d01555b <unknown> #13 0x56189cb061fd <unknown> #14 0x56189cb2494b <unknown> #15 0x56189cb24ed9 <unknown> #16 0x56189cb2793f <unknown> #17 0x7f8a659bb5d7 g_main_context_dispatch #18 0x7f8a659bb7e8 <unknown> #19 0x7f8a659bb86c g_main_context_iteration #20 0x56189cb27805 <unknown> #21 0x56189cb4bcb4 <unknown> #22 0x56189c80c69b <unknown> #23 0x56189b6c9307 <unknown> #24 0x56189b6cc082 <unknown> #25 0x56189b6c55da <unknown> #26 0x56189c7e1bde <unknown> #27 0x56189c7ebec8 <unknown> #28 0x56189c7e0b24 <unknown> #29 0x56189afb219f ChromeMain #30 0x7f8a5cce545a __libc_start_main #31 0x56189afb202a _start r8: 0000000000000000 r9: 00007ffd390e8720 r10: 0000000000000008 r11: 0000000000000246 r12: 00007f8a5d688cc0 r13: 00007ffd390e8e18 r14: 0000000000000078 r15: 00007ffd390e8e10 di: 0000000000000002 si: 00007ffd390e8720 bp: 00007ffd390e8970 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007f8a5ccf9e80 sp: 00007ffd390e8720 ip: 00007f8a5ccf9e80 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes Chrome version: 64.0.3282.24 Channel: beta OS Version: Flash Version:
,
Dec 19 2017
Unable to reproduce the issue on chromium version 64.0.3282.0 and on the latest canary 65.0.3294.5 using Ubuntu 14.04, Windows 10 and Mac 10.13.1 with the below mentioned steps. 1. Lainched Chromium 2. Navigated to chrome://settings/siteData 3. Typied something in search field 4. And tried deleting some few cookies Note: Also checked the issue on chrome version 64.0.3282.24 We observed cookies got deleted and chromium didn't crash. Ataching the screen cast of the same. @Reporter: Could you please check the screen cast and let us know if we have missed any steps in reproducing the issue. Any further inputs from your end helps us to triage the issue in a better way. Thanks!
,
Dec 19 2017
I doubt you will be able to reproduce the crash when Chromium is fully launched. This happens only in the first few minutes, while Chromium is still loading its resources. Most likely a race condition in that complex beast of code.
,
Dec 19 2017
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 20 2017
@ingo_brunberg -- Thanks for providing the feedback. Could you please provide the Crash ID from chrome://crashes/ for the related Crash. This would really help us in further triaging the issue. Thanks in advance!
,
Dec 21 2017
Sorry, crash reporting is not available in Chromium. To reproduce the bug, I would rephrase the first step as follows: 1. Start Chromium with a big, messy profile, loaded from a slow harddisk, and then immediately access the cookie manager.
,
Dec 21 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
,
Dec 26 2017
Tested on Ubuntu 14.04 using the latest Chrome Beta #64.0.3282.39 and not able to reproduce the issue. Could someone from MTV please look into the issue as mentioned in the C#6.
,
Jan 16 2018
,
Oct 23
I have experienced this issue several times, particularly when hitting Enter on the search box on the cookies page. Windows Chrome 69.0.3497.100 (Official Build) (64-bit) (cohort: Stable) Crash log uploaded: Uploaded Crash Report ID 54cb22746263fcf2 (Local Crash ID: 29363e19-95fc-499c-92be-24543771b0a4)
,
Oct 23
https://crash.corp.google.com/browse?q=expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27settings%3A%3ACookiesViewHandler%3A%3AHandleGetDisplayList%27#-propertyselector,productname:1000,productversion:100,-magicsignature:50,-magicsignature2:50,-stablesignature:50 Looks like the crash is since M63, with a spike in incidence rate in M67. All desktop platforms are affected. dschuyler added this check in M63 [1], but they no longer work on Chrome. ccing reviewer dpapad. [1]: https://chromium-review.googlesource.com/c/chromium/src/+/714241
,
Oct 23
,
Oct 25
Marking Untriaged per #11
,
Oct 26
Updating labels.
,
Dec 10
Issue 913401 has been merged into this issue.
,
Jan 9
Hi , I am facing this issue from last one month,and I can reproduce it if required (happened twice when I searched for Amazon in last two times).Can someone please take this up for fixing it.
,
Jan 9
,
Jan 10
I also get this on mondern Surface Pro (so not slow disk, not messy profile, fast machine) - also happens for browser/tab instances which have been open for a while so diagnostic at #6 is not representative of my case. However is intermittent. 71.0.3578.98 (Official Build) (64-bit)
,
Jan 21
(2 days ago)
,
Jan 21
(2 days ago)
Can someone please triage and assign this issue. I thought since it is crash bug it would be at least a bit higher in priority compared to other bugs. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 18 2017