Potential jank caused by AppBannerManagerAndroid at startup |
|||
Issue descriptionWe 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: 3a5a4906746e3264 b807c286ca22528a f50c84ad9ac817b7 549c94582bd378ef 0ec495600f47828a Go to crash/ReportID to view the traces. The stack trace that was hit the most: __ioctl <skipped java frames> banners::AppBannerManagerAndroid::AppBannerManagerAndroid(content::WebContents*) TabHelpers::AttachTabHelpers(content::WebContents*) Java_org_chromium_chrome_browser_tab_Tab_nativeInitWebContents art::ClassLinker::ResolveMethodExceptionHandlerTypes() banners::AppBannerManagerAndroid::AppBannerManagerAndroid(content::WebContents*) TabHelpers::AttachTabHelpers(content::WebContents*) Java_org_chromium_chrome_browser_tab_Tab_nativeInitWebContents
,
Nov 16
,
Nov 18
The only thing AppBannerManagerAndroid does at startup is use the JNI to call into Java and create a Java object. I would be unsurprised if there were several other objects doing equal or more amounts of work in a tab helper constructor.
,
Dec 17
ssid@ can you use the trace landed in #1 to narrow this down and possibly reassign? |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Nov 16