ipc_channel_reader.cc IPC message is too big: 150494744 |
||||||||
Issue descriptionStart the Blimp engine and client and load https://en.m.wikipedia.org/wiki/Main_Page Tap on the menu button on top left, and then tap on another point. This currently results in a client crash which destroys the BlimpConnection on the engine. The engine crashes when destroying the BlimpEngineSession with the following trace: [90831:90831:0314/185538:FATAL:surface_manager.cc(284)] Check failed: valid_surface_id_namespaces_.count(parent_namespace) == 1u (0 vs. 1) #0 0x7f4221b081fe base::debug::StackTrace::StackTrace() #1 0x7f4221b687df logging::LogMessage::~LogMessage() #2 0x7f42230b3fc5 cc::SurfaceManager::UnregisterSurfaceNamespaceHierarchy() #3 0x7f421ebb7148 content::DelegatedFrameHost::ResetCompositor() #4 0x7f421e7d6f16 content::RenderWidgetHostViewAura::RemovingFromRootWindow() #5 0x7f421e7dbeae content::RenderWidgetHostViewAura::WindowObserver::OnWindowRemovingFromRootWindow() #6 0x7f422203118e aura::Window::NotifyRemovingFromRootWindow() #7 0x7f422202ed2c aura::Window::RemoveChildImpl() #8 0x7f422202c283 aura::Window::RemoveChild() #9 0x7f422202baa4 aura::Window::~Window() #10 0x7f422202c369 aura::Window::~Window() #11 0x7f421e7cf18f content::RenderWidgetHostViewAura::Destroy() #12 0x7f421e7a99a1 content::RenderWidgetHostImpl::Destroy() #13 0x7f421e7aaed3 content::RenderWidgetHostImpl::ShutdownAndDestroyWidget() #14 0x7f421e79c79b content::RenderViewHostImpl::ShutdownAndDestroy() #15 0x7f421e2658f0 content::FrameTree::ReleaseRenderViewHostRef() #16 0x7f421e2b5fb1 content::RenderFrameHostImpl::~RenderFrameHostImpl() #17 0x7f421e2b61f9 content::RenderFrameHostImpl::~RenderFrameHostImpl() #18 0x7f421d94854f std::default_delete<>::operator()() #19 0x7f421e2e70dc std::unique_ptr<>::reset() #20 0x7f421e2e67c9 std::unique_ptr<>::~unique_ptr() #21 0x7f421e2da1f5 content::RenderFrameHostManager::~RenderFrameHostManager() #22 0x7f421e26edf5 content::FrameTreeNode::~FrameTreeNode() #23 0x7f421e2640a2 content::FrameTree::~FrameTree() #24 0x7f421ea59113 content::WebContentsImpl::~WebContentsImpl() #25 0x7f421ea59429 content::WebContentsImpl::~WebContentsImpl() #26 0x00000041697f std::default_delete<>::operator()() #27 0x00000043288c std::unique_ptr<>::reset() #28 0x00000042eed1 blimp::engine::BlimpEngineSession::~BlimpEngineSession()
,
Mar 15 2016
when client is killed, engine crashes as in #0.
,
Mar 15 2016
easier way to produce. Start Client and navigate to https://www.wikipedia.org/. Engine crashes with (there is IPC channel error, message is too big) [5741:5768:0315/160143:VERBOSE2:blimp_message_pump.cc(42)] ReadNextPacket [5741:5768:0315/160143:ERROR:ipc_channel_reader.cc(332)] IPC message is too big: 150494744 [5741:5768:0315/160143:VERBOSE2:blimp_message_output_buffer.cc(63)] OutputBuffer::ProcessMessage <BlimpMessage type=NAVIGATION subtype=NAVIGATION_STATE_CHANGED loading=false target_tab_id=0 byte_size=14> [5741:5768:0315/160143:VERBOSE2:blimp_connection.cc(66)] Sender::ProcessMessage <BlimpMessage type=NAVIGATION subtype=NAVIGATION_STATE_CHANGED loading=false target_tab_id=0 byte_size=16> [5741:5768:0315/160143:VERBOSE2:blimp_connection.cc(92)] OnWritePacketComplete, result=0 [5741:5768:0315/160143:VERBOSE2:blimp_message_output_buffer.cc(144)] Write complete, result=0 [5741:5741:0315/160143:FATAL:surface_manager.cc(284)] Check failed: valid_surface_id_namespaces_.count(parent_namespace) == 1u (0 vs. 1) #0 0x7f4a801d258e base::debug::StackTrace::StackTrace() #1 0x7f4a80232b6f logging::LogMessage::~LogMessage() #2 0x7f4a8177cfc5 cc::SurfaceManager::UnregisterSurfaceNamespaceHierarchy() #3 0x7f4a7d26dda8 content::DelegatedFrameHost::ResetCompositor() #4 0x7f4a7ce8dad6 content::RenderWidgetHostViewAura::RemovingFromRootWindow() #5 0x7f4a7ce92a6e content::RenderWidgetHostViewAura::WindowObserver::OnWindowRemovingFromRootWindow() #6 0x7f4a806fb18e aura::Window::NotifyRemovingFromRootWindow() #7 0x7f4a806f8d2c aura::Window::RemoveChildImpl() #8 0x7f4a806f6283 aura::Window::RemoveChild() #9 0x7f4a806f5aa4 aura::Window::~Window() #10 0x7f4a806f6369 aura::Window::~Window() #11 0x7f4a7ce85d4f content::RenderWidgetHostViewAura::Destroy() #12 0x7f4a7ce85cec content::RenderWidgetHostViewAura::RenderProcessGone() #13 0x7f4a7ce699c1 content::RenderWidgetHostImpl::RendererExited() #14 0x7f4a7ce4f83f content::RenderViewHostImpl::RenderProcessExited() #15 0x7f4a7ce2c6b7 content::RenderProcessHostImpl::ProcessDied() #16 0x7f4a7ce2de0e content::RenderProcessHostImpl::OnChannelError() #17 0x7f4a7af32b70 IPC::ChannelProxy::Context::OnDispatchError() #18 0x7f4a7af37349 _ZN4base8internal15RunnableAdapterIMN3IPC12ChannelProxy7ContextEFvvEE3RunIJEEEvPS4_DpOT_ #19 0x7f4a7af372b9 _ZN4base8internal12InvokeHelperILb0EvNS0_15RunnableAdapterIMN3IPC12ChannelProxy7ContextEFvvEEEE8MakeItSoIJPS5_EEEvS8_DpOT_ #20 0x7f4a7af37285 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0EEEENS0_9BindStateINS0_15RunnableAdapterIMN3IPC12ChannelProxy7ContextEFvvEEEFvPS8_EJSC_EEENS0_12InvokeHelperILb0EvSB_EEFvvEE3RunEPNS0_13BindStateBaseE #21 0x7f4a801b296e base::Callback<>::Run() #22 0x7f4a801d7f7e base::debug::TaskAnnotator::RunTask() #23 0x7f4a8024f97f base::MessageLoop::RunTask() #24 0x7f4a8024fc08 base::MessageLoop::DeferOrRunPendingTask() #25 0x7f4a8024fdd2 base::MessageLoop::DoWork() #26 0x7f4a802634ae base::MessagePumpLibevent::Run() #27 0x7f4a8024f3af base::MessageLoop::RunHandler() #28 0x7f4a802e4324 base::RunLoop::Run() #29 0x7f4a7c6dbe76 content::BrowserMainLoop::MainMessageLoopRun() #30 0x7f4a7c6dbbd1 content::BrowserMainLoop::RunMainMessageLoopParts() #31 0x7f4a7c6e4865 content::BrowserMainRunnerImpl::Run() #32 0x7f4a7c6d5b06 content::BrowserMain() #33 0x7f4a7e230616 content::RunNamedProcessTypeMain() #34 0x7f4a7e2324ed content::ContentMainRunnerImpl::Run() #35 0x7f4a7e22fa92 content::ContentMain() #36 0x000000415c95 main #37 0x7f4a75b92ec5 __libc_start_main #38 0x000000415b79 <unknown>
,
Mar 15 2016
Looks like this is caused by the big message from CC to browser process.
,
Mar 17 2016
the DCHECK failure is caused by the issue describe in https://bugs.chromium.org/p/chromium/issues/detail?id=595497. We still need solve IPC message size issue.
,
Mar 21 2016
,
Mar 22 2016
,
Mar 23 2016
Does anyone know if this is a blocker for v0.5? In other words, do we need to fix this before we can have a system that works well enough for people to start to using it? Grace, this is assigned to Tommy, but he's out for a week. If this ends up a blocker for v0.5 is there someone else it should be assigned to?
,
Mar 23 2016
150M in one IPC message? That is a lot. If that is a common case, we need to reconsider whether we choose the right layer. For most of the sites, I believe they are blocked due to issue 597026 . So I don't think this is P1.
,
Mar 23 2016
I'm not able to reproduce the error with the IPC message. There is an error concerning the tap scenario, its been filed at crbug/590102.
,
Dec 9 2016
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by haibinlu@chromium.org
, Mar 15 2016