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:
137a0a23bb0f094a ,1320.281
af82ea8ef208ccf8 ,399.136
b1f15f9a06437cfb ,325.592
8ba72ae8a70d907e ,261.942

Go to crash/ReportID to view the traces.

The stack trace that was hit the most:

<skipped java frames>
android::LayerTitleCache::GetTitleLayer(int)
android::TabLayer::SetProperties(int, bool, int, int, int, int, int, int, int, int, int, bool, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, float, bool, int, int, int, bool, bool, int, int, float, float, float, float, bool)
Java_org_chromium_chrome_browser_compositor_scene_1layer_TabListSceneLayer_nativePutTabLayer
<skipped java frames>
android::CompositorView::UpdateLayerTreeHost()
content::CompositorImpl::UpdateLayerTreeHost()
cc::SingleThreadProxy::DoBeginMainFrame(viz::BeginFrameArgs const&)
cc::SingleThreadProxy::BeginMainFrame(viz::BeginFrameArgs const&)
base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
base::MessageLoopImpl::DoWork()
base::MessagePumpForUI::OnNonDelayedLooperCallback()
base::(anonymous namespace)::NonDelayedLooperCallback(int, int, void*)