Check failed: apartment_type == GetComApartmentTypeForThread() |
|||
Issue descriptionChrome Version: 69 ToT commit 300c6052043f60782f89a471135218ac5cfb340f OS: Win10 What steps will reproduce the problem? (1) Run Chrome with assertions enabled. (2) Type into location bar. What is the expected result? Can type text. What happens instead? [26648:45576:0612/164322.900:FATAL:com_init_util.cc(75)] Check failed: apartment_type == GetComApartmentTypeForThread() (2 vs. 1) Backtrace: base::debug::StackTrace::StackTrace [0x00007FFDB09078F4+36] (D:\chromium\src\base\debug\stack_trace_win.cc:286) logging::LogMessage::~LogMessage [0x00007FFDB0934D8F+95] (D:\chromium\src\base\logging.cc:593) base::win::AssertComApartmentType [0x00007FFDB0A3D508+168] (D:\chromium\src\base\win\com_init_util.cc:76) ui::OnScreenKeyboardDisplayManagerInputPane::EnsureInputPanePointers [0x00007FFDA9148306+80] (D:\chromium\src\ui\base\ime\win\on_screen_keyboard_display_manager_input_pane.cc:90) ui::OnScreenKeyboardDisplayManagerInputPane::TryShow [0x00007FFDA9147DA6+28] (D:\chromium\src\ui\base\ime\win\on_screen_keyboard_display_manager_input_pane.cc:159) base::debug::TaskAnnotator::RunTask [0x00007FFDB090921E+382] (D:\chromium\src\base\debug\task_annotator.cc:101) base::internal::IncomingTaskQueue::RunTask [0x00007FFDB094A5CE+126] (D:\chromium\src\base\message_loop\incoming_task_queue.cc:131) base::MessageLoop::RunTask [0x00007FFDB094ECC9+665] (D:\chromium\src\base\message_loop\message_loop.cc:320) base::MessageLoop::DeferOrRunPendingTask [0x00007FFDB094F3C7+183] (D:\chromium\src\base\message_loop\message_loop.cc:329) base::MessageLoop::DoWork [0x00007FFDB094F61E+542] (D:\chromium\src\base\message_loop\message_loop.cc:373) base::MessagePumpForUI::DoRunLoop [0x00007FFDB09531C9+169] (D:\chromium\src\base\message_loop\message_pump_win.cc:174) base::MessagePumpWin::Run [0x00007FFDB0952B18+104] (D:\chromium\src\base\message_loop\message_pump_win.cc:58) base::MessageLoop::Run [0x00007FFDB094E6B8+136] (D:\chromium\src\base\message_loop\message_loop.cc:273) base::RunLoop::Run [0x00007FFDB099C389+249] (D:\chromium\src\base\run_loop.cc:105) ChromeBrowserMainParts::MainMessageLoopRun [0x00007FFD9A6FE2D4+226] (D:\chromium\src\chrome\browser\chrome_browser_main.cc:2198) content::BrowserMainLoop::RunMainMessageLoopParts [0x00007FFD97555DD4+72] (D:\chromium\src\content\browser\browser_main_loop.cc:985) content::BrowserMainRunnerImpl::Run [0x00007FFD97559785+169] (D:\chromium\src\content\browser\browser_main_runner_impl.cc:170) content::BrowserMain [0x00007FFD97551D9C+228] (D:\chromium\src\content\browser\browser_main.cc:51) content::RunBrowserProcessMain [0x00007FFD9813E700+212] (D:\chromium\src\content\app\content_main_runner_impl.cc:620) content::ContentMainRunnerImpl::Run [0x00007FFD9813F2E9+509] (D:\chromium\src\content\app\content_main_runner_impl.cc:970) service_manager::Main [0x00007FFDBED5591F+1790] (D:\chromium\src\services\service_manager\embedder\main.cc:459) content::ContentMain [0x00007FFD9813E5CF+67] (D:\chromium\src\content\app\content_main.cc:19) ChromeMain [0x00007FFD994F11E4+332] (D:\chromium\src\chrome\app\chrome_main.cc:104) MainDllLoader::Launch [0x00007FF781F83B8F+627] (D:\chromium\src\chrome\app\main_dll_loader_win.cc:201) wWinMain [0x00007FF781F818AF+2223] (D:\chromium\src\chrome\app\chrome_exe_main_win.cc:230) __scrt_common_main_seh [0x00007FF78204BA9E+262] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283) BaseThreadInitThunk [0x00007FFDE3113034+20] RtlUserThreadStart [0x00007FFDE52E1551+33]
,
Jun 13 2018
Getting this here too in a ToT debug build, it's been awhile since I've done a Windows build so could always be something I've done wrong but I'm getting this failure on a build from last night.
,
Jun 13 2018
That's for the report, I'll give this a bisect then.
,
Jun 14 2018
Hi Dave, could this be related to https://chromium.googlesource.com/chromium/src.git/+/e6c18518bbcc4fb0ca88aa7d11214021abad09d9 ? The stack trace goes through input pane code.
,
Jun 14 2018
Confirmed that https://chromium.googlesource.com/chromium/src/+/e6c18518bbcc4fb0ca88aa7d11214021abad09d9 is when this crash started happening.
,
Jun 14 2018
Duplicate of issue 852317. Fixed this afternoon.
,
Jun 14 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by alancutter@chromium.org
, Jun 12 2018