ThreadTaskRunnerHandle DCHECK in layout tests |
|||
Issue descriptionSee for example https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29/builds/69657 / https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.webkit%2FWebKit_Android__Nexus4_%2F69657%2F%2B%2Frecipes%2Fsteps%2Fstack_tool_with_logcat_dump%2F0%2Fstdout: [7031:7031:0921/142700.121988:320779590:FATAL:thread_task_runner_handle.cc(29)] Check failed: current. Error: This caller requires a single-threaded context (i.e. the current task needs to run from a SingleThreadTaskRunner). signal 6 (SIGABRT) at 0x00001b77 (code=-6), thread 7031 (ntent_shell_apk) pid: 7031, tid: 7031, name: ntent_shell_apk >>> org.chromium.content_shell_apk <<< signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- r0 00000000 r1 00001b77 r2 00000006 r3 00000000 r4 00000006 r5 0000001e r6 00001b77 r7 0000010c r8 bec0d840 r9 000000e0 sl bec0dd90 fp 00000000 ip 00000001 sp bec0d798 lr 400b0fe5 pc 400bff90 Stack Trace: RELADDR FUNCTION 00021f90 tgkill+12 00012fe1 pthread_kill+48 000131f5 raise+10 00011f2b <unknown> 00021844 abort+4 0047606d base::debug::BreakDebugger()+20 004865cf logging::LogMessage::~LogMessage()+926 004bd83d base::ThreadTaskRunnerHandle::Get()+112 0049d099 base::RunLoop::RunLoop(base::RunLoop::Type)+92 013d1007 LayoutTestBrowserMain(content::MainFunctionParams const&, std::__ndk1::unique_ptr<content::BrowserMainRunner, std::__ndk1::default_delete<content::BrowserMainRunner> > const&)+766 0132aef1 content::RunNamedProcessTypeMain(std::__ndk1::basic_string<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> > const&, content::MainFunctionParams const&, content::ContentMainDelegate*)+96 0132b39b content::ContentMainRunnerImpl::Run()+206 00ac1427 service_manager::Main(service_manager::MainParams const&)+650 00d8c8b3 Java_org_chromium_content_app_ContentMain_nativeStart+118 +Gab for ThreadTaskRunnerHandle, +Mike/Peter as content shell OWNERS
,
Sep 22 2017
This means that LayoutTestBrowserMain() doesn't have a MessageLoop (or other RunLoop::Delegate) when it tries to RunLoop Le jeu. 21 sept. 2017 12 h 43, yzshen via monorail < monorail+v2.1922036758@chromium.org> a écrit :
,
Sep 22 2017
Yuzhu, the second-to-last stack frame is service_manager::Main. I figured if LayoutTestBrowserMain is started as a service in the wrong environment, that might have something to do with Mojo. (I couldn't find a component for services/).
,
Sep 22 2017
RE #3: I think service_manager::Main() is an entry point which now shows up in every call stack. It is called very early and delegates to its embedder for further initialization / execution logic. And agreed with gab@ that this is an issue of missing MessageLoop.
,
Oct 13 2017
This has been consistently green. |
|||
►
Sign in to add a comment |
|||
Comment 1 by yzshen@chromium.org
, Sep 21 2017