Crash: init crash reporting happens twice. |
||||
Issue descriptionEVE + latest canary (R72-11259.0.0) + ToT (1bdcf632f33) Debug build sometimes crash: [8190:8232:1113/162903.459712:FATAL:breakpad_linux.cc(806)] Check failed: !g_breakpad. #0 0x55dd24b94e78 base::debug::StackTrace::StackTrace() #1 0x55dd2492109c base::debug::StackTrace::StackTrace() #2 0x55dd2496a0fa logging::LogMessage::~LogMessage() #3 0x55dd2df621d7 breakpad::(anonymous namespace)::EnableCrashDumping() #4 0x55dd2df61c6d breakpad::InitCrashReporter() #5 0x55dd1afdc76d _ZN4base8internal13FunctorTraitsIPFvRKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEEvE6InvokeIRKSC_JSA_EEEvOT_DpOT0_ #6 0x55dd1afdc72d _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIRKPFvRKNSt3__112basic_stringIcNS4_11char_traitsIcEENS4_9allocatorIcEEEEEJSC_EEEvOT_DpOT0_ #7 0x55dd1afdc6f0 _ZN4base8internal7InvokerINS0_9BindStateIPFvRKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEEEJS9_EEEFvvEE7RunImplIRKSD_RKNS3_5tupleIJS9_EEEJLm0EEEEvOT_OT0_NS3_16integer_sequenceImJXspT1_ #8 0x55dd1afdc62c _ZN4base8internal7InvokerINS0_9BindStateIPFvRKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEEEJS9_EEEFvvEE3RunEPNS0_13BindStateBaseE #9 0x55dd19b9313c _ZNO4base12OnceCallbackIFvvEE3RunEv #10 0x55dd24be93d8 base::debug::TaskAnnotator::RunTask() #11 0x55dd24ad0866 base::internal::TaskTracker::RunOrSkipTask() #12 0x55dd24bc6c1c base::internal::TaskTrackerPosix::RunOrSkipTask() #13 0x55dd24ace1a8 base::internal::TaskTracker::RunAndPopNextTask() #14 0x55dd24c16675 base::internal::SchedulerWorker::RunWorker() #15 0x55dd24c15d79 base::internal::SchedulerWorker::RunPooledWorker() #16 0x55dd24c15bff base::internal::SchedulerWorker::ThreadMain() #17 0x55dd24bc8256 base::(anonymous namespace)::ThreadFunc() #18 0x7b08a143a4fe <unknown> #19 0x7b089fbd2bef clone This is just in OOBE, first boot. (Probably it does not depend on the boot type.)
,
Dec 1
This crash is still here. (ToT 09489a7f4d6727c8c0cfe72eb8032eccc478c051 )
,
Dec 3
,
Dec 3
breakpad::InitCrashReporter() is getting called twice in the same process. Given it is coming from a PostTask(), it's easy to grep for "InitCrashReporter," and see this is coming from WizardController::OnChangedMetricsReportingState().
,
Dec 4
Crash reporter initialization in WizardController was added in http://codereview.chromium.org/7480040 . But it looks like since then initialization has changed and this branch needs to be revised.
,
Dec 4
Adding antrim@ who is working on OOBE flow on ChromeOS these days. |
||||
►
Sign in to add a comment |
||||
Comment 1 by alemate@chromium.org
, Nov 14