Android WebView bfcache tile leak?

[minchuang kuang]

Hi, I would like to know if there is ongoing support for Android WebView. Our team has developed an app using the WebView solution, and we are currently using version M143. During our testing, we discovered an issue that has been present since version M116. The problem is as follows: When we enable bfcache, enter a page, click a link to jump to another page, and then repeatedly perform "back" and "forward" navigation approximately thirty times, the following warning appears: "WARNING: tile memory limits exceeded, some content may not draw" Consequently, the page content begins to disappear. Based on our analysis, we found that the current tile memory issue is a "leak" in numerical terms only; in reality, there is no leak in the memory allocated by malloc. The root cause is that after repeated forward and backward operations, surfaces within the viz module are repeatedly created and destroyed. The associated tile resources are not notified to the ResourcePool in the cc module via ReturnResource for release, resulting in resources being continuously created while the number of busy resources accumulates. As for why the surface destruction does not notify the ResourcePool via ReturnResource, I suspect it is a timing issue. The notification to the ResourcePool must pass through objects such as CompositorFrameSinkSupport, SynchronousCompositorHost, and SynchronousCompositorProxy, which are destroyed before the notification to destroy the Tile resources can be sent. Has Google identified this issue? Is there an intention to resolve this Android WebView problem? We have attempted some fixes and would like to know if we should submit them upstream. Thank you very much!