headless: Received signal 11 SEGV_MAPERR
Reported by
xivans1...@gmail.com,
Sep 6 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/60.0.3112.113 Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: Periodically Chrome crashes on different pages (after restart same pages won't cause crash). Received signal 11 SEGV_MAPERR 000000000000 #0 0x56126f6bf757 base::debug::StackTrace::StackTrace() #1 0x56126f6bf2cf base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x7f436107f390 <unknown> #3 0x56126e7c2e9c content::RenderWidgetHostImpl::OnSnapshotFromSurfaceReceived() #4 0x56126e58032a content::CopyFromCompositingSurfaceHasResult() #5 0x56126e7d0c50 _ZN4base8internal7InvokerINS0_9BindStateIPFvRKN3gfx4SizeE11SkColorTypeRKNS_8CallbackIFvRK8SkBitmapN7content16ReadbackResponseEELNS0_8CopyModeE1ELNS0_10RepeatModeE1EEENSt3__110unique_ptrIN3viz16CopyOutputResultENSK_14default_deleteISN_EEEEEJS4_S7_SH_EEEFvSQ_EE7RunOnceEPNS0_13BindStateBaseEOSQ_ #6 0x56127013cfbf viz::CopyOutputRequest::SendResult() #7 0x56127013ce14 viz::CopyOutputRequest::~CopyOutputRequest() #8 0x5612700c92cd cc::Layer::Inputs::~Inputs() #9 0x5612720387cd cc::SurfaceLayer::~SurfaceLayer() #10 0x5612706013e4 ui::Layer::~Layer() #11 0x5612706017d9 ui::Layer::~Layer() #12 0x5612705ed2e0 aura::Window::~Window() #13 0x5612705ed809 aura::Window::~Window() #14 0x56126e7b8ce0 content::RenderWidgetHostImpl::Destroy() #15 0x56126e7b6799 content::RenderViewHostImpl::ShutdownAndDestroy() #16 0x56126e61b59c content::FrameTree::ReleaseRenderViewHostRef() #17 0x56126e63b41d content::RenderFrameHostImpl::~RenderFrameHostImpl() #18 0x56126e63be09 content::RenderFrameHostImpl::~RenderFrameHostImpl() #19 0x56126e6576f2 content::RenderFrameHostManager::~RenderFrameHostManager() #20 0x56126e61c842 content::FrameTreeNode::~FrameTreeNode() #21 0x56126e61a479 content::FrameTree::~FrameTree() #22 0x56126e88517d content::WebContentsImpl::~WebContentsImpl() #23 0x56126e8855f9 content::WebContentsImpl::~WebContentsImpl() #24 0x561271e51355 headless::HeadlessWebContentsImpl::~HeadlessWebContentsImpl() #25 0x561271e51429 headless::HeadlessWebContentsImpl::~HeadlessWebContentsImpl() #26 0x561271e53dfc headless::HeadlessBrowserContextImpl::DestroyWebContents() #27 0x5612732f22e6 headless::HeadlessDevToolsManagerDelegate::CloseTarget() #28 0x5612732f3ded _ZN4base8internal7InvokerINS0_9BindStateIMN8headless31HeadlessDevToolsManagerDelegateEFNSt3__110unique_ptrINS_15DictionaryValueENS5_14default_deleteIS7_EEEEiPKS7_EJNS0_17UnretainedWrapperIS4_EEEEEFSA_iSC_EE3RunEPNS0_13BindStateBaseEOiOSC_ #29 0x5612732f3715 headless::HeadlessDevToolsManagerDelegate::HandleCommand() #30 0x56126e58f8a0 content::DevToolsSession::Dispatch() #31 0x56126e580f0d content::BrowserDevToolsAgentHost::DispatchProtocolMessage() #32 0x56126e587376 content::DevToolsHttpHandler::OnWebSocketMessage() #33 0x56126f6bfe8b base::debug::TaskAnnotator::RunTask() #34 0x56126f6d7c1b base::MessageLoop::RunTask() #35 0x56126f6d828b base::MessageLoop::DoWork() #36 0x56126f6d9739 base::MessagePumpGlib::Run() #37 0x56126f6f6630 base::RunLoop::Run() #38 0x56126e542a64 content::BrowserMainLoop::MainMessageLoopRun() #39 0x56126e54285e content::BrowserMainLoop::RunMainMessageLoopParts() #40 0x56126e5452ed content::BrowserMainRunnerImpl::Run() #41 0x5612730cfa1a headless::HeadlessContentMainDelegate::RunProcess() #42 0x56126f3c6737 content::RunNamedProcessTypeMain() #43 0x56126f3c718d content::ContentMainRunnerImpl::Run() #44 0x56126f3ced34 service_manager::Main() #45 0x56126f3c5cd2 content::ContentMain() #46 0x561271e55b15 headless::(anonymous namespace)::RunContentMain() #47 0x561271e55b8c headless::HeadlessBrowserMain() #48 0x56126f3ccb17 headless::HeadlessShellMain() #49 0x56126df9a2fe ChromeMain #50 0x7f435acf0830 __libc_start_main #51 0x56126df9a150 <unknown> r8: 0000000000000001 r9: 000056126e7c2e60 r10: 000008fe17f752a8 r11: 00007f435ae66350 r12: 0000000000000000 r13: 000008fe1b387600 r14: 0000000000000000 r15: 0000000000000001 di: 000008fe1b387640 si: 0000000000000001 bp: 0000000000000001 bx: 00007fff96f16868 dx: 0000000000000000 ax: 0000000000000000 cx: 00007fff96f16868 sp: 00007fff96f166f0 ip: 000056126e7c2e9c efl: 0000000000010246 cgf: 009d000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. What is the expected behavior? What went wrong? Headless Chrome crashed Did this work before? N/A Chrome version: 62.0.3195 Channel: dev OS Version: Ubuntu 16.04 4.4.0-93-generic Flash Version: running in Docker
,
Sep 7 2017
How can i access chrome://crashes page in headless mode?
I have tried something like this, but it seems this page is not available in headless:
> {"params":{"url":"chrome://crashes"},"method":"Page.navigate","id":1}
< {"id":1,"result":{"frameId":"21729.1"}}
> {"params":{"expression":"new XMLSerializer().serializeToString(document.body)"},"method":"Runtime.evaluate","id":2}
< {"id":2,"result":{"result":{"type":"string","value":"\u003Cbody xmlns=\"http://www.w3.org/1999/xhtml\"\u003E\u003C/body\u003E"}}}
,
Sep 7 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@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
,
Sep 8 2017
Confirming that the above issue is related to headless mode. Hence, marking it as untriaged and adding appropriate labels for further triage.
,
Sep 11 2017
Could you provide steps to reproduce the crash? It looks like you were trying to get a snapshot, is that right? You can use --enable-crash-reporter --crash-dumps-dir=/tmp/crash/ flags to grab the crash report also, but knowing what docker config you are using will be also very helpful. Thanks!
,
Sep 11 2017
dvallet, yes, here is my pipeline 1. Open connection 2. Render 3. Take screenshot 4. Run custom scripts 5. Close connection (full ws dump for single page in attachment) Unfortunately i cannot provide crash dump because 1. it crashes periodically on different sites (so i cannot reproduce it locally) 2. i have already switched cluster to stable Chrome build (61) and this issue is not reproducible on it
,
Sep 11 2017
,
Nov 16 2017
Assigning to dvallet@ for further triage.
,
Nov 20 2017
Apologies for the late reply, If this is working on stable then I'd rather close the issue for now. Otherwise, I'd need at least an URL to investigate on, which I haven't found on the dump. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jmukthavaram@chromium.org
, Sep 7 2017Labels: Needs-Triage-M62 Needs-Feedback