Chrome_ChromeOS: Crash Report - extensions::EventRouter::DoDispatchEventToSenderBookkeepingOnUI |
|||||||||||||
Issue descriptionreporter:stevehuang@google.com Magic Signature: extensions::EventRouter::DoDispatchEventToSenderBookkeepingOnUI Crash link: https://crash.corp.google.com/browse?q=product_name%3D%27Chrome_ChromeOS%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27extensions%3A%3AEventRouter%3A%3ADoDispatchEventToSenderBookkeepingOnUI%27&stbtiq=&reportid=&index=0 ------------------------------------------------------------------------------- Sample Report ------------------------------------------------------------------------------- Product name: Chrome_ChromeOS Magic Signature : extensions::EventRouter::DoDispatchEventToSenderBookkeepingOnUI Product Version: 70.0.3538.58 Process type: browser Report ID: 83ca6f462db2673b Report Url: https://crash.corp.google.com/83ca6f462db2673b Report Time: 2018-10-22T14:42:10-07:00 Upload Time: 2018-10-22T14:54:11.928-07:00 Uptime: 8082951 ms OS Name: Linux OS Version: 0.0.0 Linux 3.18.0-18544-g5667a3e8072f #1 SMP PREEMPT Thu Oct 11 01:55:12 PDT 2018 x86_64 CPU Architecture: amd64 CPU Info: family 6 model 76 stepping 4 ------------------------------------------------------------------------------- Crashing thread: Thread index: 0. Stack Quality: 99%. Thread id: 8674. ------------------------------------------------------------------------------- 0x000061077913b526 (chrome - event_router.cc) extensions::EventRouter::DoDispatchEventToSenderBookkeepingOnUI(void*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, extensions::events::HistogramValue, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) 0x0000610777be9fe2 (chrome - callback.h: 99) base::MessageLoop::DoWork() 0x0000610777bf91a5 (chrome - message_pump_libevent.cc: 210) base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) 0x000061077a802343 (chrome - run_loop.cc: 102) <name omitted> 0x000061077a3e140f (chrome - chrome_browser_main.cc: 2080) ChromeBrowserMainParts::MainMessageLoopRun(int*) 0x0000610778a94f3b (chrome - browser_main_loop.cc: 1039) content::BrowserMainLoop::RunMainMessageLoopParts() 0x0000610778a98701 (chrome - browser_main_runner_impl.cc: 161) content::BrowserMainRunnerImpl::Run() 0x0000610778a8cd7c (chrome - browser_main.cc: 47) content::BrowserMain(content::MainFunctionParams const&) 0x000061077a3ccfe0 (chrome - content_main_runner_impl.cc: 537) content::ContentMainRunnerImpl::Run(bool) 0x000061077a3d4e6b (chrome - main.cc: 472) service_manager::Main(service_manager::MainParams const&) 0x0000610777d140c4 (chrome - content_main.cc: 19) ChromeMain 0x0000798169861735 (libc-2.23.so - libc-start.c: 289) __libc_start_main 0x0000610777d04178 (chrome + 0x00357178) _start 0x00007fff508640c7 ------------------------------------------------------------------------------- Manual regression range finder link ------------------------------------------------------------------------------- https://crash.corp.google.com/browse?q=expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27extensions%3A%3AEventRouter%3A%3ADoDispatchEventToSenderBookkeepingOnUI%27#-property-selector,-samplereports,+productname,+productversion:1000,+directory,-clientid,+operatingsystem,+url,+simplifiedurl,+extensions
,
Oct 23
Sorry, I'm not familiar with this code at all, so can't really suggest a sensible owner either.
,
Nov 8
,
Nov 9
I'll take a look.
,
Nov 21
Issue 907506 has been merged into this issue.
,
Dec 3
,
Dec 3
Issue 890606 has been merged into this issue.
,
Dec 3
Can we remove the restricted-view? The reporters on 870838 can't access this one.
,
Dec 3
,
Dec 6
Adding reporters from 870838 since this one is restricted-view.
,
Dec 10
#10, was able to reproduce most of what is showing in https://crbug.com/870838#c73 where I only failed to reproduce the quantity test. Sent feedback the times it crashed with this bug number and 870838 in the description. At the time of writing this, there are only 3 reports from December 6 and no new ones have appeared: 1e4157a9fd6c4e26 5097ed3af0f6b577 f0ad77386330009b Logs are attached.
,
Dec 10
Scratch that, 3 new crash ids came in: 1ef291e9878952d1 61c7d0e86a0b7bfa 3db9bf4f8f092f09
,
Dec 14
,
Dec 19
Issue 910942 has been merged into this issue.
,
Jan 2
Issue 918448 has been merged into this issue.
,
Jan 3
Issue 917660 has been merged into this issue.
,
Jan 8
Issue 919354 has been merged into this issue.
,
Jan 14
Some users (at crbug/870838) state that while they have crash reporting enabled, this crash happens without adding a trace in chrome://crashes.
,
Jan 14
Issue 919193 has been merged into this issue.
,
Jan 14
Issue 912110 has been merged into this issue.
,
Jan 16
(6 days ago)
(Copied from 870838) Updated to M73 dev and this is now effecting the browser as well, but crashes when you close a tab. I know this is not the same issue, but it has the same behavior as described in previous comments. Here are the bug reports from today: a32038f44da039b1 29f41641f6fd4783 98660633ea4ffb79 754c12a83d880c54 f17f896fcdff8a7a 5ee87b784787a1a0 ba8194088c39c47c
,
Jan 16
(6 days ago)
Issue 922659 has been merged into this issue.
,
Jan 17
(5 days ago)
#21: 754c12a83d880c54 is this issue. The others are on: views::FocusSearch::FindNextFocusableViewImpl Might it be related, or we should file another bug for that?
,
Jan 18
(5 days ago)
Removing Restrict-View as several other bugs are merged with this one but the reports do not have access to it.
,
Jan 18
(5 days ago)
Issue 917619 has been merged into this issue.
,
Jan 18
(5 days ago)
I could FINALLY reproduce it using the extension mentioned in crbug/917619.
,
Jan 18
(4 days ago)
Regarding Comment 18 ("this crash happens without adding a trace in chrome://crashes"), I found while collecting information for Issue 917619 that after this crash occurs, even if crash reporting has been enabled, no crash shows up in chrome://crashes. However, after some time has passed (I checked after some tens of minutes), the crash does show up.
It's as if crash data is being collected in the background with some delay.
,
Today
(11 hours ago)
I reported crbug/917660 which was duped into this. I can readily reproduce this on my Pixelbook 100% of the time. Opening an incognito window and opening any website and then closing the incognito window invariably crashes the machine (goes to black screen, desktop re-appears after a few seconds and Chrome offers to re-open tabs).
,
Today
(8 hours ago)
I do not have the PIA extension from crbug/917619, and I'm seeing crashes. Note that I'm on beta. I can reproduce it like in Comment 28, although it took 4 attempts for me. I've had a similar crash in the past when closing notifications from an incognito window, but I can't remember when it last happened. If it happens again, I'll open a new bug report for it. If I can do anything within reason to help, let me know. I should have put in a bug report months ago - or whenever it started happening. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by stevehuang@google.com
, Oct 22Labels: M71 M70 XAct