We collected slow reports from users facing janks and found that the function mentioned above is taking too much time on the main thread, potentially causing janks.
The issue can be found in reports:
dd57debc83d5c5ba ,2198.09 ms
930844faa4b59f2b ,581.757 ms
Go to crash/ReportID to view the traces.
The stack trace that was hit the most:
nanosleep / lock / malloc
<skipped java stack>
content::WebContentsObserverProxy::DidFinishNavigation(content::NavigationHandle*)
content::WebContentsImpl::DidFinishNavigation(content::NavigationHandle*)
content::NavigationHandleImpl::~NavigationHandleImpl()
content::NavigationHandleImpl::~NavigationHandleImpl()
content::NavigatorImpl::DidNavigate(content::RenderFrameHostImpl*, FrameHostMsg_DidCommitProvisionalLoad_Params const&, std::__ndk1::unique_ptr<content::NavigationHandleImpl, std::__ndk1::default_delete<content::NavigationHandleImpl> >, bool)
content::RenderFrameHostImpl::DidCommitNavigationInternal(FrameHostMsg_DidCommitProvisionalLoad_Params*, bool)
content::RenderFrameHostImpl::DidCommitProvisionalLoad(std::__ndk1::unique_ptr<FrameHostMsg_DidCommitProvisionalLoad_Params, std::__ndk1::default_delete<FrameHostMsg_DidCommitProvisionalLoad_Params> >, mojo::InterfaceRequest<service_manager::mojom::InterfaceProvider>)
content::mojom::FrameHostStubDispatch::Accept(content::mojom::FrameHost*, mojo::Message*)
mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept(mojo::Message*)
_ZN3IPC12_GLOBAL__N_132ChannelAssociatedGroupController19AcceptOnProxyThreadEN4mojo7MessageE$908b0a2b9dcb3d6c3dee58ef8dd98270
base::internal::Invoker<base::internal::BindState<void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::*)(mojo::Message), scoped_refptr<IPC::(anonymous namespace)::ChannelAssociatedGroupController>, base::internal::PassedWrapper<mojo::Message> >, void ()>::Run(base::internal::BindStateBase*)
base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
base::MessageLoop::RunTask(base::PendingTask*)
base::MessageLoop::DoWork()
base::MessagePumpForUI::OnNonDelayedLooperCallback()
base::(anonymous namespace)::NonDelayedLooperCallback(int, int, void*)
Comment 1 by bugdroid1@chromium.org
, Nov 15